On 07/02/16 16:55, frowand.list@xxxxxxxxx wrote: > From: Frank Rowand <frank.rowand@xxxxxxxxxxx> > > 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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
