Re: [PATCH 0/4] pinctrl single support for SoC specific features
* Linus Walleij linus.wall...@linaro.org [130722 14:01]: On Wed, Jul 10, 2013 at 2:24 PM, Tony Lindgren t...@atomide.com wrote: 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? OK but I still need to look closer at them as well, so no guarantee I will pull it... Good comments, let's try to make it all transparent. I'll drop my branch and will repost the patches when I have things working using irqchip. Regards, Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/4] pinctrl single support for SoC specific features
On Wed, Jul 10, 2013 at 2:24 PM, Tony Lindgren t...@atomide.com wrote: 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? OK but I still need to look closer at them as well, so no guarantee I will pull it... Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/4] pinctrl single support for SoC specific features
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 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/4] pinctrl single support for SoC specific features
* Roger Quadros rog...@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. Linus, does that sound OK to you? Regards, Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 0/4] pinctrl single support for SoC specific features
On 07/10/2013 03:24 PM, Tony Lindgren wrote: * Roger Quadros rog...@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 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
