| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CADRPPNS3riBaC_onHKAFn2X_tnW5Z0=a2zyxfZy1f77oEe2Jbw@mail.gmail.com> Date: Thu, 7 Jun 2012 12:10:28 +0800 From: Li Yang <leoli@...escale.com> To: Scott Wood <scottwood@...escale.com> Cc: Wood Scott-B07421 <B07421@...escale.com>, Li Yang-R58472 <r58472@...escale.com>, Zhao Chenhui-B35336 <B35336@...escale.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org> Subject: Re: [PATCH v5 4/5] fsl_pmc: Add API to enable device as wakeup event source On Thu, Jun 7, 2012 at 2:29 AM, Scott Wood <scottwood@...escale.com> wrote: > On 06/05/2012 11:06 PM, Li Yang wrote: >> On Wed, Jun 6, 2012 at 2:05 AM, Scott Wood <scottwood@...escale.com> wrote: >>> You ignored "what about devices other than ethernet". >> >> No, I haven't. Other devices are so at least for now. > > I don't understand that last sentence. Other devices are what? Probably I misunderstood your question "what about devices other than ethernet". Did you mean how would other devices other than ethernet know how to set it? Other wakeup capable devices can call the API when it is up and running. It will be the pmc driver's responsibility to find out if that specific device can be configured as a wakeup source for the SoC. Leo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists