linux-kernel - Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual

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: <5778AB73.2030603@gmail.com>
Date:	Sat, 2 Jul 2016 23:06:43 -0700
From:	Frank Rowand <frowand.list@...il.com>
To:	robh+dt@...nel.org, david@...son.dropbear.id.au,
	pantelis.antoniou@...sulko.com, stephen.boyd@...aro.org,
	broonie@...nel.org, grant.likely@...retlab.ca, mark.rutland@....com
Cc:	mporter@...sulko.com, koen@...inion.thruhere.net,
	linux@...ck-us.net, marex@...x.de, wsa@...-dreams.de,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-i2c@...r.kernel.org, panto@...oniou-consulting.com
Subject: Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual

On 07/02/16 16:55, frowand.list@...il.com wrote:
> From: Frank Rowand <frank.rowand@...sony.com>
> 
> Hi All,
> 
> This is version 2 of this email.

< snip >

> The one remaining piece that this patch does not provide is how
> the overlay manager (which does not yet exist in the mainline
> tree) can apply an overlay to two different targets.  That
> final step should be a trivial change to of_overlay_create(),
> adding a parameter that is a mapping of the target (or maybe
> even targets) in the overlay to different targets in the
> active device tree.
> 
> This seems like a more straight forward way to handle connectors.
> 
> First, ignoring pinctrl and pinmux, what does everyone think?
> 
> Then, the next step is whether pinctrl and pinmux work with this method.
> Pantelis, can you point me to a good example for
> 
>   1) an in-tree board dts file
>   2) an overlay file (I am assuming out of tree) that applies to the board
>   3) an in-tree .dtsi file that would provide the same features as
>      the overlay file if it was included by the board dts file
> 
> It should be easier to discuss pinctrl and pinmux with an example.

And I should have added that there are other complexities beyond
pinctrl and pinmux that are not addressed.  Baby steps first,
before the whole enchilada.

-Frank