[PATCH v4] ARM: SPEAr600: Add device-tree support to SPEAr600 boards
Stefan Roese
sr at denx.de
Fri Mar 16 23:34:11 EST 2012
On Friday 16 March 2012 13:14:35 Arnd Bergmann wrote:
> On Friday 16 March 2012, Stefan Roese wrote:
> > v4:
> > - Added memory node to all dts/dtsi files
> > - Reorganizes bus topology in the dtsi file, to match the
> >
> > real SoC layout
>
> Looks good.
>
> > +
> > + ahb {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + compatible = "simple-bus";
> > + ranges;
> > +
> > + vic0: interrupt-controller at f1100000 {
> > + compatible = "arm,pl190-vic";
> > + interrupt-controller;
> > + reg = <0xf1100000 0x1000>;
> > + #interrupt-cells = <1>;
> > + };
> > +
> > ...
> > + apb {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + compatible = "simple-bus";
> > + ranges;
> > +
> > + serial at d0000000 {
> > + compatible = "arm,pl011", "arm,primecell";
> > + reg = <0xd0000000 0x1000>;
> > + interrupt-parent = <&vic0>;
> > + interrupts = <24>;
> > + };
> > ...
> > + };
> > + };
> > +};
>
> I would prefer to see non-empty ranges properties here. I expected the
> buses to be contiguous address ranges per bus, but apparently that
> is not the case -- you have 0xd... and 0xf... on both of them.
Yes, Its quite ugly.
> The simplest ranges property would be to have in the ahb node:
>
> ranges = <0xd0000000 0xd0000000 0x30000000>;
>
> Which just means that the bus is limited to those addresses (if that is
> indeed the case -- I don't know much about ahb and apb).
Okay, I'll add those ranges. Even though I personally don't find it more
descriptive this way.
Thanks,
Stefan
More information about the devicetree-discuss
mailing list