"Premi, Sanjeev" <[email protected]> writes: > I was trying other way - understand if there is an existing norm/ > convention that I can follow - rather than (re)invent it!
The existing norm is that omap_devices are never destroyed. The same is true for the way we handle platform_devices that are not omap_devices. That being said, it doesn't answer the question of how we would destroy them if we wanted to, and that does indeed deserve some discussion. However, I think your confusion is more about the separation between device code and driver code. It is the responsibility of device init code (arch/arm/*omap*) to create and register devices with the system. This is where platform_devices and omap_devices are handled currently. The drivers then register themselves (as platform_drivers) with the driver core, and the driver core hooks them together. The goal we're working towards is that the drivers be generic, and should not know anything about device-specific registration. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
