On Sun, 2009-11-22 at 16:02 -0700, Grant Likely wrote:

quoted

+       /* devices contained int the flipper chipset */
+       soc {

It would be better to rename this as IMMR or the bus type.  This node
doesn't actually describe the entire chip, but describes the internal
memory mapped registers.

I would really just call it "flipper" :-)

quoted

+               #address-cells = <1>;
+               #size-cells = <1>;
+               #interrupt-cells = <1>;
+               model = "flipper";

Drop the model property

quoted

+               compatible = "nintendo,flipper";
+               clock-frequency = <162000000>; /* 162MHz */
+               ranges = <0x0c000000 0x0c000000 0x00010000>;

Since you're only doing 1:1 mappings; you could replace this with an
empty "ranges;" property instead.

On the other hand it is a useful "documentation" to specify the exact
range decoded when you know it :-) For non documented HW I prefer when
the DT contains as precise information as possible. It also allows, if
so wished, to create proper hierarchical struct resource in the kernel
that represent the bus hierarchy in a nicer way. So I vote for keeping
that in.

quoted

+
+               video@0c002000 {
+                       compatible = "nintendo,flipper-video";
+                       reg = <0x0c002000 0x100>;
+                       interrupts = <8>;
+                       interrupt-parent = <&pic>;

Hint:  If you move the interrupt-parent property up to the root node,
then you don't need to specify it in every single device node; it will
just inherit from the parent.

Note that this is a linux-ism no ? (aka ePAPRism). If they aim toward
having a real OF which I think they do they may wish to pass on this
trick.

quoted

+                       /* XFB is the eXternal FrameBuffer */
+                       xfb-start = <0x01698000>; /* end-of-ram - xfb-size */
+                       xfb-size = <0x168000>;

Can 'xfb' be made a second tuple to the 'reg' property so that all the
address mapping code works on it?  ie:

reg = <0x0c002000 0x100
       0x01698000 0x168000>;

At the very least, it is wise to adopt the same form as the reg
property when describing address ranges instead of splitting it into
multiple properties.

I agree with using the same form as reg. I'm not sure about using "reg",
it depends. Albert, is that xfb location something that is configurable
or is it fixed ? If it's configurable, it could remain a separate
property I suppose, since it overlaps main memory, it's a bit fishy to
have it in "reg"... you do seem to strip off the fb from the memory
"reg" property though... Maybe the right thing to do is to leave the
memory "reg" property to be the whole RAM and just reserve the area
covered by the fb ?

quoted

+               /* External Interface bus */
+               exi@0c006800 {
+                       #address-cells = <1>;
+                       #size-cells = <1>;
+                       compatible = "nintendo,flipper-exi";
+                       reg = <0x0c006800 0x40>;
+                       interrupts = <4>;
+                       interrupt-parent = <&pic>;
+
+                       USBGECKO0: usbgecko@0c006814 {
+                               compatible = "usbgecko,usbgecko";
+                               reg = <0x0c006814 0x14>;
+                               virtual-reg = <0xcc006814>;
+                       };
+               };
+        };
+};
+

Shouldn't the above be dynamically detected ?

Cheers,
Ben.