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
| ||
|
Date: Fri, 11 Oct 2013 11:45:39 +0300 From: Roger Quadros <rogerq@...com> To: Tony Lindgren <tony@...mide.com> CC: <devicetree@...r.kernel.org>, Grygorii Strashko <grygorii.strashko@...com>, Linus Walleij <linus.walleij@...aro.org>, <linux-kernel@...r.kernel.org>, Peter Ujfalusi <peter.ujfalusi@...com>, Prakash Manjunathappa <prakash.pm@...com>, Haojian Zhuang <haojian.zhuang@...aro.org>, BenoƮt Cousson <bcousson@...libre.com>, <linux-omap@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 4/6] pinctrl: single: Add support for wake-up interrupts On 10/10/2013 07:23 PM, Tony Lindgren wrote: > * Tony Lindgren <tony@...mide.com> [131010 09:09]: >> * Roger Quadros <rogerq@...com> [131010 06:32]: >>> >>> I tried testing this with the USB EHCI driver, but I'm not getting wake up interrupts >>> while the system is still running and only the EHCI controller is runtime suspended. >>> >>> It seems we need to somehow call _reconfigure_io_chain() to update the daisy chain >>> whenever the pad wakeup_enable bit is changed. >> >> Sounds like this is on omap3? Have you tried calling pcs_soc->rearm() in the >> pcs_irq_handle() like the comments there suggest? At least for me that keeps >> the wake-up interrupts continuously running on omap3 instead of just idle modes. >> >> Now on omap4, I've noticed the wake up interrupts are on all the time based on tests >> with the serial driver. > > Oh, and if you're runtime suspending EHCI only, and if the EHCI module has > wake-up registers, it should be able to wake EHCI from retention on it's own > without a need for the io chain at all. > The problem is that the asynchronous wake up mechanism for USB Host module is broken in the design so we have to rely on IO daisy chain every time. :( cheers, -roger -- 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