open-pic device tree node and subnodes for additional functionality?

Kumar Gala galak at kernel.crashing.org
Tue Feb 17 03:58:42 EST 2009


On Freescale open-pic controllers we have a number of additional  
features not spec'd per openpic.  (additional timers, perf mon, PCIe  
msi, message interrupts, ...).  The problem is how to identify these  
features in the device tree.

For example we have:

                 msi at 41600 {
                         compatible = "fsl,mpc8572-msi", "fsl,mpic-msi";
                         reg = <0x41600 0x80>;
                         msi-available-ranges = <0 0x100>;
                         interrupts = <
                                 0xe0 0
                                 0xe1 0
                                 0xe2 0
                                 0xe3 0
                                 0xe4 0
                                 0xe5 0
                                 0xe6 0
                                 0xe7 0>;
                         interrupt-parent = <&mpic>;
                 };

                 mpic: pic at 40000 {
                         interrupt-controller;
                         #address-cells = <0>;
                         #interrupt-cells = <2>;
                         reg = <0x40000 0x40000>;
                         compatible = "chrp,open-pic";
                         device_type = "open-pic";
                 };

---

should we put msi under the pic node as a child and add ranges, etc.   
The question that raises in my mind is what does the reg property end  
up meaning.  I assume it shouldn't stay as is.

- k



More information about the Linuxppc-dev mailing list