* DebBarma, Tarun Kanti <tarun.kanti@xxxxxx> [110304 11:50]: > > In that case we have to associate probably a dev attribute to system timer. > Do you have alternate proposal? No need for that. Keep the system timer code to the minimum so it does not have any unnecessary dependencies. That code needs to be running early and efficient, while the other timers should really be a device driver. You can have shared timer read/write functions that don't depend on dev. And you can just tag the pysical timer used for system timer as reserved. Then you can initialize the other timers later on and skip the system timer. For the other timers you can have dev oriented timer read/write wrapper functions for the other timers. Cheers, Tony -- 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
