linux-kernel - Re: [PATCH v1 1/6] dt-bindings: misc: add document for reboot-mode driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAAtXAHfkfqELHamMVK3-6UE+LtVwimA7oe=QEzfF2WyrHXxcaQ@mail.gmail.com>
Date:	Wed, 23 Dec 2015 00:37:22 -0800
From:	Moritz Fischer <moritz.fischer@...us.com>
To:	Rob Herring <robh@...nel.org>
Cc:	Andy Yan <andy.yan@...k-chips.com>, heiko@...ech.de,
	Arnd Bergmann <arnd@...db.de>, john.stultz@...aro.org,
	sjg@...omium.org,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	treding@...dia.com, Kumar Gala <galak@...eaurora.org>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	wxt@...k-chips.com, Catalin Marinas <catalin.marinas@....com>,
	olof@...om.net, geert+renesas@...der.be,
	linux-rockchip@...ts.infradead.org,
	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	Sebastian Reichel <sre@...nel.org>, jun.nie@...aro.org,
	"pawel.moll@....com" <pawel.moll@....com>,
	Will Deacon <will.deacon@....com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Devicetree List <devicetree@...r.kernel.org>,
	Russell King <linux@....linux.org.uk>,
	Greg KH <gregkh@...uxfoundation.org>, joel@....id.au,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	lorenzo.pieralisi@....com, khilman@...aro.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v1 1/6] dt-bindings: misc: add document for reboot-mode driver

Rob,

On Tue, Dec 22, 2015 at 4:32 PM, Rob Herring <robh@...nel.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/