pinctrl single support for SoC specific features
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 3/4 | pinctrl: single: omap: Add SoC specific module for wake-up eventsdrivers/ drivers/ include/ | +21 | 1 reply | |
| 3/4 | pinctrl: single: omap: Add SoC specific module for wake-up events | +0 | 1 reply | |
| 4/4 | ARM: OMAP: Move DT wake-up event handling over to use pinctrl-single-omaparch/ arch/ arch/ +3 more | +40 | 1 reply | |
| 4/4 | ARM: OMAP: Move DT wake-up event handling over to use pinctrl-single-omap | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] pinctrl single support for SoC specific features
Hi Tony,
Quoted 13 lines · Tony Lindgren
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.
Quoted 5 lines
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