linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] pinctrl single support for SoC specific features
Date: Wed, 10 Jul 2013 16:14:21 +0300	[thread overview]
Message-ID: <51DD5E2D.50504@ti.com> (raw)
In-Reply-To: <20130710122417.GT5523@atomide.com>

On 07/10/2013 03:24 PM, Tony Lindgren wrote:
> * Roger Quadros <rogerq@ti.com> [130710 05:16]:
>> 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.
> 
> How about I'll push an immutable branch against v3.11-rc1 when it's
> tagged and send a pull request to Linus W for the first three patches?
> 
> That way we can base other branches on this if needed.

Looks good to me. Thanks.

cheers,
-roger

  reply	other threads:[~2013-07-10 13:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 20:50 [PATCH 0/4] pinctrl single support for SoC specific features Tony Lindgren
2013-06-07 20:50 ` [PATCH 1/4] pinctrl: single: Prepare for supporting " Tony Lindgren
2013-06-08  9:37   ` Haojian Zhuang
2013-06-08 15:27     ` Tony Lindgren
2013-06-09  5:21       ` Haojian Zhuang
2013-07-22 21:15       ` Linus Walleij
2013-07-29  8:57         ` Tony Lindgren
2013-06-07 20:50 ` [PATCH 2/4] pinctrl: single: Add hardware specific hooks for IRQ and GPIO wake-up events Tony Lindgren
2013-06-09  4:46   ` Haojian Zhuang
2013-06-10 15:36     ` Tony Lindgren
2013-07-22 21:44       ` Linus Walleij
2013-07-29  8:50         ` Tony Lindgren
2013-06-07 20:50 ` [PATCH 3/4] pinctrl: single: omap: Add SoC specific module for " Tony Lindgren
2013-06-08 15:29   ` Tony Lindgren
2013-06-09  5:28   ` Haojian Zhuang
2013-06-10 10:03   ` Quadros, Roger
2013-06-10 15:21     ` Tony Lindgren
2013-06-11 12:51       ` Roger Quadros
2013-06-12 13:33         ` Tony Lindgren
2013-07-22 22:03   ` Linus Walleij
2013-07-22 22:06   ` Linus Walleij
2013-06-07 20:50 ` [PATCH 4/4] ARM: OMAP: Move DT wake-up event handling over to use pinctrl-single-omap Tony Lindgren
2013-06-07 20:52   ` Tony Lindgren
2013-06-10 15:36     ` Tony Lindgren
2013-06-10 12:31   ` Quadros, Roger
2013-06-10 14:25     ` Tony Lindgren
2013-06-11  9:08       ` Roger Quadros
2013-07-10 12:10 ` [PATCH 0/4] pinctrl single support for SoC specific features Roger Quadros
2013-07-10 12:24   ` Tony Lindgren
2013-07-10 13:14     ` Roger Quadros [this message]
2013-07-22 20:54     ` Linus Walleij
2013-07-29  8:59       ` Tony Lindgren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51DD5E2D.50504@ti.com \
    --to=rogerq@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).