linux-kernel - Re: An extremely simplified pinctrl bindings proposal

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]

Date:	Mon, 6 Feb 2012 20:26:52 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mitch Bradley <wmb@...mworks.com>
Cc:	Stephen Warren <swarren@...dia.com>,
	Dong Aisheng <dongas86@...il.com>,
	Shawn Guo <shawn.guo@...aro.org>,
	Dong Aisheng-B29396 <B29396@...escale.com>,
	"Sascha Hauer (s.hauer@...gutronix.de)" <s.hauer@...gutronix.de>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"kernel@...gutronix.de" <kernel@...gutronix.de>,
	"cjb@...top.org" <cjb@...top.org>,
	"Simon Glass (sjg@...omium.org)" <sjg@...omium.org>,
	Thomas Abraham <thomas.abraham@...aro.org>,
	"Grant Likely (grant.likely@...retlab.ca)" 
	<grant.likely@...retlab.ca>,
	"ext Tony Lindgren (tony@...mide.com)" <tony@...mide.com>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: An extremely simplified pinctrl bindings proposal

On Mon, Feb 6, 2012 at 8:05 PM, Mitch Bradley <wmb@...mworks.com> wrote:

> I like the general approach of simplifying the pinctrl thing, as the
> previous approach did not appear to be converging.

pinctrl as such is upstream, widely ACKed and quite converged I'd say.

But the Device Tree bindings and general path to get data out of the drivers
and board files are not (yet) converging...

> Both Open Firmware and ACPI have addressed this general problem.  In
> addition to a numeric identifier for the register, you need to specify the
> access semantics.  It's difficult to finitely enumerate all possible cases,
> but you can get to 99.9% with a modest number of access models, and then add
> new models as needed.

This is interesting. So are you referring to a piece of Open Firmware
that is not in the Device Tree? Since this is all about device tree that
comes from OF, we might be reinventing the wheel.
Can you give some pointers?

Indeed it seems related to ACPI or some BIOS stuff on
non-embedded systems.

Yours,
Linus Walleij
--
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/