On Wed, Nov 18, 2009 at 2:51 AM, Paul Walmsley <paul@xxxxxxxxx> wrote: > Hello Kevin, > > On Tue, 17 Nov 2009, Kevin Hilman wrote: > >> Add use counters to omap_device to enable multiple potential users of >> an omap_device. This is needed if ever there are multiple users or >> multiple instances of a driver with a single omap_device. >> >> Without usecounting, with multiple users, the first one to call idle >> may forcibly idle the device while other users are still active. > > Could you please send along an example of the use case for this? I would > prefer not to add usecounting at this layer unless it is absolutely > necessary, since only one driver should be bound to a device at a time. OK, after some more wrangling with the UART layer, I don't think I will need this patch. If an omap_device is bound to a single driver, the driver itself can do the usecounting and will be more effecient when doing so. Note however that this will prevent any direct replacement of clk_enable/disable with omap_device_enable/disable since some drivers are built on the assumption that the clk API does usecounting. Kevin -- 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
