Hi Niklas, On Thu, Jan 18, 2018 at 1:24 AM, Niklas Söderlund <niklas.soderlund@xxxxxxxxxxxx> wrote: > On 2018-01-17 17:17:03 +0100, Simon Horman wrote: >> Add soc node to represent the bus and move all nodes with a base address >> into this node. This is consistent with handling of R-Car Gen3, RZ/G1, and >> R-Car V2H (R8A77920) SoCs upstream. It is intended to migrate other R-Car >> Gen2 SoCs to this scheme. >> >> The ordering is derived from simply moving each node with an address up to >> before any nodes without a base address that occur before the soc node. To >> improve maintainability follow-up patches will sort subnodes of both the >> new soc node and the root node. >> >> This patch should not introduce any functional change. >> >> Signed-off-by: Simon Horman <horms+renesas@xxxxxxxxxxxx> > > The 'ranges' property in the soc node is new. I checked the > documentation and as far as I can make out this is how it should be. But > I'm not certain why :-) Please see section 2.3.8 in the Device Tree Specification, either from ePAPR, or at https://www.devicetree.org/. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
