Grant Likely wrote: > Now is probably a good time to mention that there is *nothing* in the > device tree that enforces a 1:1 relationship between device tree nodes > and driver instances. Sure, it make sense to register the i2s and > codec drivers from probing on the i2s and codec nodes. However, there > is nothing that prevents the codec driver from *also* registering a > fabric driver based on a property in the codec node or the board-level > compatible property.
Wouldn't it make more sense for the fabric driver to register the codec driver? The fabric driver is the "master" of the other drivers, should it needs to load and run first. > Fabric drivers are codec specific anyway. Yes and no. They're really platform-specific, but they should be able to scan the device tree, determine which codecs are actually on the system, and then link in the appropriate codec driver. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
