On 11/18/07, Segher Boessenkool <[EMAIL PROTECTED]> wrote: > > David Gibson > > made a proposal that a fabric node wrap the codec node. That doesn't > > work very well with the i2c bus where the bus code is walking down the > > nodes and triggering the instantiation of the i2c drivers. > > Yeah, doesn't work at all. > > > But what about putting the fabric node inside the codec node? > > _Which_ codec node? Having more than one isn't uncommon at all.
In all of them. Fabric can probably be split into pieces that corresponds to the codec. > There is no way you can describe this fabric stuff in a generic way in > the device tree. Just hardcode it in your platform support code; if > the platform code supports several variant boards, _it_ can probe that > from the device tree (in whatever way works for that platform). The codec-fabric node was just being used to trigger the loading of the platform specific driver. > > > Segher > > -- Jon Smirl [EMAIL PROTECTED] _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
