From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Quadros Subject: Re: [PATCH 0/4] pinctrl single support for SoC specific features Date: Wed, 10 Jul 2013 15:10:24 +0300 Message-ID: <51DD4F30.7050603@ti.com> References: <20130607203936.16513.57494.stgit@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from devils.ext.ti.com ([198.47.26.153]:42577 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753758Ab3GJMLA (ORCPT ); Wed, 10 Jul 2013 08:11:00 -0400 In-Reply-To: <20130607203936.16513.57494.stgit@localhost> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Tony Lindgren Cc: linus.walleij@linaro.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Hi Tony, On 06/07/2013 11:50 PM, Tony Lindgren wrote: > Hi all, > > Here are few patches to add support for SoC specific features > to pinctrl-single. This is needed at least for omaps to support > IO chain wake-up events from deeper idle states. > > With this patch series, device drivers can request named pinctrl > states like active and idle from the PM runtime suspend and resume > calls to set the wake enable bits for selected pins. Further > the device driver can toggle the wake-up feature as needed based on > the device_may_wakeup() state set by the standard sysfs > power/wakeup entry. > > This is implemented in a separate pinctrl-single-omap driver that > works together with pinctrl-single. This way the SoC specific > are separated from the common pinctrl-single, and allows a relatively > easy way to implement SoC specific things like wake-up events, > pin interrupts, and GPIO. What's the status of this? Would be nice to get it in 3.12. I'm basing the OMAP USB host wakeup support on this. cheers, -roger