Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1435915

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

From Frank Rowand <frowand.list@gmail.com>
Newsgroups linux.kernel
Subject Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual
Date 2016-07-03 08:10 +0200
Message-ID <rQILn-5dF-7@gated-at.bofh.it> (permalink)
References <rQCZj-1uM-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[RFC PATCH 0/1] Portable Device Tree Connector -- conceptual frowand.list@gmail.com - 2016-07-03 02:00 +0200
  Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-03 08:10 +0200
  Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Mark Brown <broonie@kernel.org> - 2016-07-04 17:30 +0200
    Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-04 20:20 +0200
  Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Pantelis Antoniou <panto@antoniou-consulting.com> - 2016-07-05 20:10 +0200
    Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-06 19:50 +0200
  Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual David Gibson <david@gibson.dropbear.id.au> - 2016-07-08 02:50 +0200
    Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Pantelis Antoniou <pantelis.antoniou@konsulko.com> - 2016-07-08 09:30 +0200
      Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual David Gibson <david@gibson.dropbear.id.au> - 2016-07-08 09:50 +0200
      Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-08 21:30 +0200
        Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-08 21:30 +0200
    Re: [RFC PATCH 0/1] Portable Device Tree Connector -- conceptual Frank Rowand <frowand.list@gmail.com> - 2016-07-08 21:30 +0200

csiph-web