Hi!
> > I see no reason such policies would need to apply to a system as
> > a whole. The first policy already is supported. The second would need some
> > kernel support, but most can be done in user space.
>
> I didn't details that second type of policy, but I'm thinking about
> the kinds of situation where user mode logic is impractical since
> the device drivers have to switch operating modes ... e.g. to the
> sort of mode where clocks are gated (by hardware or software)
> or voltages adjusted according to load. Not unlike governors with
> cpufreq: policies set in userspace, but implemented by low level
> magic that's unsafe for userspace.
Which devices can not be handled by userspace logic?
I guess that for some devices you really want device-resume in kernel
(ide disk), but can easily do device-suspend in userspace
(hdparm -y).
Are there devices that need even suspend in kernel?
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
