MIME-Version: 1.0
In-Reply-To: <20151223003217.GA18700@rob-hp-laptop>
References: <1450774949-23901-1-git-send-email-andy.yan@rock-chips.com>
	<1450775124-23966-1-git-send-email-andy.yan@rock-chips.com>
	<20151223003217.GA18700@rob-hp-laptop>
Date: Wed, 23 Dec 2015 00:37:22 -0800
Message-ID: <CAAtXAHfkfqELHamMVK3-6UE+LtVwimA7oe=QEzfF2WyrHXxcaQ@mail.gmail.com>
Subject: Re: [PATCH v1 1/6] dt-bindings: misc: add document for reboot-mode driver
From: Moritz Fischer <moritz.fischer@ettus.com>
To: Rob Herring <robh@kernel.org>
Cc: Andy Yan <andy.yan@rock-chips.com>, heiko@sntech.de,
        Arnd Bergmann <arnd@arndb.de>, john.stultz@linaro.org,
        sjg@chromium.org,
        Alexandre Belloni <alexandre.belloni@free-electrons.com>,
        treding@nvidia.com, Kumar Gala <galak@codeaurora.org>,
        Ian Campbell <ijc+devicetree@hellion.org.uk>, wxt@rock-chips.com,
        Catalin Marinas <catalin.marinas@arm.com>, olof@lixom.net,
        geert+renesas@glider.be, linux-rockchip@lists.infradead.org,
        Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
        Sebastian Reichel <sre@kernel.org>, jun.nie@linaro.org,
        "pawel.moll@arm.com" <pawel.moll@arm.com>,
        Will Deacon <will.deacon@arm.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Devicetree List <devicetree@vger.kernel.org>,
        Russell King <linux@arm.linux.org.uk>,
        Greg KH <gregkh@linuxfoundation.org>, joel@jms.id.au,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        lorenzo.pieralisi@arm.com, khilman@linaro.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Mark Rutland <mark.rutland@arm.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1158
Lines: 33

Rob,

On Tue, Dec 22, 2015 at 4:32 PM, Rob Herring <robh@kernel.org> wrote:

> I would like to see the property names here standardized as much as
> possible. I'm not sure if we can define the properties as a u32 or need
> some flexibility here.

Quick question, semi on topic. I have a similar case (and a driver in
the pipeline),
however all I got is a (persistent over reboot) hardware register to
which I can write whatever.
On the other side I'd have u-boot pull out the value, but as it's up
to u-boot to
implement whatever it does with this info I'm kinda struggling with the idea
of a standardized binding. In my case I'd like it to go into 'safe
mode' or 'firmware update'.

With loader = <0xace0ba5e>, <0xdeadbeef> ... and loader-names <> I
could have u-boot read the values
from fdt at boot. Then again I'm not describing hardware, but specific
settings ...

Would that be acceptable?

Cheers,

Moritz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/