On 3/21/07, Shaohua Li <shaohua.li@xxxxxxxxx> wrote: > On Wed, 2007-03-21 at 02:30 +0800, Pavel Machek wrote: > > No, that's not how it works; look at hda_audio, it already has > > powersave. Just power down audio card 5 seconds after its control file > > is closed. > It's another case of doing policy in a driver. > IMHO, this kind of policy is best handled inside the driver because it is specific to the hardware. This will ensure that the driver will just work on every distro without some userspace policy being present and setup _correctly_. In the above case if the driver runs on a single architecture, chances are you can figure out what the best value (5s) for that arch is and hardwire it. If the driver indeed runs on multiple architectures that have drastically different notions of the optimum values, then I guess it could be exposed through sysfs. Even then, it doesn't seem likely that the value would be changed from what it is initialized to. I have yet to come across drivers where you change these values several times at runtime. If I am simply being ignorant, I would appreciate some examples. Regards, Amit -- Amit Kucheria, NOKIA _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
