Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757972Ab3JJQA1 (ORCPT ); Thu, 10 Oct 2013 12:00:27 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:32860 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757851Ab3JJQAZ (ORCPT ); Thu, 10 Oct 2013 12:00:25 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 50.131.214.131 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+uVYl1g2rZ4Ct1hBYY8eur Date: Thu, 10 Oct 2013 09:00:19 -0700 From: Tony Lindgren To: Roger Quadros Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Grygorii Strashko , Linus Walleij , linux-kernel@vger.kernel.org, Peter Ujfalusi , Prakash Manjunathappa , Haojian Zhuang , =?utf-8?Q?Beno=C3=AEt?= Cousson , linux-omap@vger.kernel.org Subject: Re: [PATCH 4/6] pinctrl: single: Add support for wake-up interrupts Message-ID: <20131010160018.GA29913@atomide.com> References: <20131003054104.8941.88857.stgit@localhost> <20131003054221.8941.87801.stgit@localhost> <5256AA7F.8030005@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5256AA7F.8030005@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1610 Lines: 36 * 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. > I think pcs_irq_set_wake() is where need to control system wakeup behaviour for the irq. > This is where we should be able to change WAKEUP_EN bit of the pad > to enable/disable system wakeup for that pad and also call _reconfigure_io_chain(). Well the irq_set_wake() should only be needed for suspend and resume. For runtime PM the wake-events should be always enabled by default as pointed out by Alan Stern a while back. > This would mean that we don't really need to set WAKEUP_EN for the pads in the DTS file. Well for runtime PM, we should also do the automatic handling if configured. But how to do that best is still open.. Regards, Tony -- 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/