podgov exposes different scaling schemes. Only the most common
scheme, scaling based on busy/idle events, had proper module_busy
and module_idle guaranteed. Userspace and framerate based policies
did not explicitly enable device and this may have lead to usage of
hardware when it is not powered.