Re: [RFC] Tying sysfs "wakeup" file to platform-level?handler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 24 2008, at 23:19, Rafael J. Wysocki was caught saying:
> > Maybe there is some other way to do this that I don't quite grok?
> > Right now, the i8042 device does not have the can_wakeup flag set
> > so writing either "enabled" or "disabled" leads to -EINVAL.
> 
> For PCI we set the can_wakeup flag during the initialization of devices.
> 
> For some other devices, ACPI BIOS contains information telling us whether
> they are capable of waking the system up and the ACPI code sets that flag for
> them on this basis.
> 
> Does your platform know which devices can wake up?

Yep. i8042, lid, power button, battery state change, WOL. I think 
I can do something similar to what ACPI is doing by trapping the
device registration.

~Deepak

-- 
 Deepak Saxena  http://www.greenbasement.info
   _____   __o  Kernel Hacker, One Laptop Per Child  (o>
------    -\<,  Give One Laptop, Get One Laptop      //\
 ----- ( )/ ( ) http://www.amazon.com/xo             V_/_
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux