The reason I'm keeping my own count is because I don't see a driver
interface to the PM subsystem that allows me to ascertain my own
usage_count. I see that the get/put routines use the atomic_t
/dev->power.usage_count/ but I can’t access that directly.
I’m trying to use the activity count to return -EBUSY from
pm_runtime_suspend to catch the case where activity comes in between
pm_runtime_idle(no activity) and pm_runtime_suspend().
that's pretty much guaranteed to not happen...
the whole logic is set up to hide all of these sequencing issues from
drivers.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
