From: Frank Rowand <frowand.list@gmail.com>
To: robh+dt@kernel.org, david@gibson.dropbear.id.au,
pantelis.antoniou@konsulko.com, stephen.boyd@linaro.org,
broonie@kernel.org, grant.likely@secretlab.ca,
mark.rutland@arm.com
Cc: mporter@konsulko.com, koen@dominion.thruhere.net,
linux@roeck-us.net, marex@denx.de, wsa@the-dreams.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, panto@antoniou-consulting.com
Subject: Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual
Date: Sat, 2 Jul 2016 23:06:43 -0700 [thread overview]
Message-ID: <5778AB73.2030603@gmail.com> (raw)
In-Reply-To: <1467503750-31703-1-git-send-email-frowand.list@gmail.com>
On 07/02/16 16:55, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@am.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
next prev parent reply other threads:[~2016-07-03 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 23:55 [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual frowand.list
2016-07-02 23:55 ` [RFC PATCH 1/1] device tree connectors, using plugs and sockets frowand.list
2016-07-03 6:06 ` Frank Rowand [this message]
2016-07-04 15:22 ` [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Mark Brown
2016-07-04 18:15 ` Frank Rowand
2016-07-05 18:01 ` Pantelis Antoniou
2016-07-06 17:40 ` Frank Rowand
2016-07-07 7:15 ` David Gibson
2016-07-08 7:26 ` Pantelis Antoniou
2016-07-08 7:43 ` David Gibson
2016-07-08 19:20 ` Frank Rowand
2016-07-08 19:25 ` Frank Rowand
2016-07-08 19:22 ` Frank Rowand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5778AB73.2030603@gmail.com \
--to=frowand.list@gmail.com \
--cc=broonie@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=koen@dominion.thruhere.net \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=mporter@konsulko.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).