Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756394Ab3JKIqb (ORCPT ); Fri, 11 Oct 2013 04:46:31 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:45068 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752272Ab3JKIqI (ORCPT ); Fri, 11 Oct 2013 04:46:08 -0400 Message-ID: <5257BAB3.50100@ti.com> Date: Fri, 11 Oct 2013 11:45:39 +0300 From: Roger Quadros User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Tony Lindgren CC: , Grygorii Strashko , Linus Walleij , , Peter Ujfalusi , Prakash Manjunathappa , Haojian Zhuang , =?ISO-8859-1?Q?Beno=EEt_Cousson?= , , Subject: Re: [PATCH 4/6] pinctrl: single: Add support for wake-up interrupts References: <20131003054104.8941.88857.stgit@localhost> <20131003054221.8941.87801.stgit@localhost> <5256AA7F.8030005@ti.com> <20131010160018.GA29913@atomide.com> <20131010162314.GD29913@atomide.com> In-Reply-To: <20131010162314.GD29913@atomide.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1456 Lines: 32 On 10/10/2013 07:23 PM, Tony Lindgren wrote: > * Tony Lindgren [131010 09:09]: >> * Roger Quadros [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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/