Thread (32 messages) 32 messages, 4 authors, 2013-07-29
STALE4730d
Revisions (3)
  1. v1 [diff vs current]
  2. v1 current
  3. v1 [diff vs current]

[PATCH 0/4] pinctrl single support for SoC specific features

From: tony@atomide.com (Tony Lindgren)
Date: 2013-07-10 12:24:17
Also in: linux-omap

* Roger Quadros [off-list ref] [130710 05:16]:
Hi Tony,

On 06/07/2013 11:50 PM, Tony Lindgren wrote:
quoted
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.

Linus, does that sound OK to you?

Regards,

Tony
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help