On Wednesday 02 November 2005 1:59 pm, Greg KH wrote:
> On Sat, Oct 29, 2005 at 09:55:41AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > * There's a writeable sysfs "wakeup" file, with one of two values:
> > > - "enabled", when the policy is to allow wakeup
> > > - "disabled", when the policy is not to allow it
> > > - "" if the device can't currently issue wakeups
> >
> > Could we either get "not-supported" value here, or remove the file if it is not
> > supported? Having empty file is ugly...
>
> Sure, have a patch for this? :)
Turns out that "remove if not supported" is impractical; I did have
that implemented, and backed it out as I got deeper into testing.
For one example, the "can wakeup" for USB devices is a function of what
configuration the device is in ... so a device with two configurations
(call them #5 and #42) as well as "unconfigured" (config #0) might
not support wakeup in two of its three states; maybe only #42 supports
remote wakeup.
Yes, those empty files bothered me a bit too.
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
