Hi Thomas, Boris, On 27/05/2015 13:23, Thomas Petazzoni wrote: > Dear Gregory CLEMENT, > > On Wed, 27 May 2015 12:20:49 +0200, Gregory CLEMENT wrote: > >> But is it really depending of the board itself? >> I see that the first lines are the same on all the dts, I just remember that >> there was a reason why we could not put it in the dtsi. > > Yes, because the DT language doesn't have a += operator, basically. > > Some of the MBus ranges are inherently board-specific: when you have a > NOR flash, you need a specific MBus range for it. And such a MBus range > is board-specific. > > Since it's not possible to do: > > ranges = <SoC level ranges> > > in .dtsi, and: > > ranges += <board level ranges> > > in .dts, we simply decided to always put: > > ranges = <SoC level and board level ranges> > > in the .dts. > > It does create some duplication, but that's the best we could do with > the existing DT infrastructure. Thanks for the remainder. So I think we should duplicate the crypto related part in all the dts file which use an Armada XP SoC. And we don't have to test it again as soon as it was tested on an Armada XP board (and it is the case with the Armada XP one). Gregory > > Best regards, > > Thomas > -- Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- 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
