My apologies for starting a new thread, but I don't have this thread in my Inbox. http://www.spinics.net/lists/linux-omap/msg81034.html Tony Lindgren wrote: >* Pantelis Antoniou <panto@xxxxxxxxxxxxxxxxxxxxxxx> [121031 15:02]: >> >> So when device's node is 'disabled' of_platform_device_create_pdata() >> will not create the device. >> >> Now, of course it is possible to re-trigger the platform's probe method >> to be called, and in fact I do so in the capebus patches. > >You should fix this in generic way then rather than working >around it in capebus. The same problem exists changing >between different functionality for the shared pins, >let's say between USB pins and UART pins if you want a >serial debug console on some phone. The current capebus solution goes a long way to fixing a huge issue for BeagleBone users and I don't understand what seems to be a push-back on principle. On BeagleBone capes, these conflicts cannot be resolved early. Do you have suggestions on some more generic method? It seems to me the proposed capebus approach strikes a good balance. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html