Message ID | 1557474150-19618-1-git-send-email-alexandre.torgue@st.com (mailing list archive) |
---|---|
Headers | show |
Series | pinctrl: stm32: add suspend/resume management | expand |
On Fri, May 10, 2019 at 9:42 AM Alexandre Torgue <alexandre.torgue@st.com> wrote: > During power sequence, GPIO hardware registers could be lost if the power > supply is switched off. Each device using pinctrl API is in charge of > managing pins during suspend/resume sequences. But for pins used as gpio or > irq stm32 pinctrl driver has to save the hardware configuration. > Each register will be saved at runtime and restored during resume sequence. Both patches applied. On the same pinctrl devel branch is also Benjamin's patches to support the "link_consumers" property on the pin controller descriptor to enable links from pin control consumers back to their pin controller suppliers, especially important for STMFX. Would you please check if it work fine if you turn on this feature for the SoC STM32 pin controller? I am working a bit on refining the patches, so I want to enable testing with some SoC pin controllers as well and possibly make the behavior default. Yours, Linus Walleij
On 5/24/19 1:24 PM, Linus Walleij wrote: > On Fri, May 10, 2019 at 9:42 AM Alexandre Torgue > <alexandre.torgue@st.com> wrote: > >> During power sequence, GPIO hardware registers could be lost if the power >> supply is switched off. Each device using pinctrl API is in charge of >> managing pins during suspend/resume sequences. But for pins used as gpio or >> irq stm32 pinctrl driver has to save the hardware configuration. >> Each register will be saved at runtime and restored during resume sequence. > > Both patches applied. > > On the same pinctrl devel branch is also Benjamin's patches to support > the "link_consumers" property on the pin controller descriptor to > enable links from pin control consumers back to their pin controller > suppliers, especially important for STMFX. > > Would you please check if it work fine if you turn on this feature > for the SoC STM32 pin controller? > Sure. Either today or next Monday. I let you know. regards Alex > I am working a bit on refining the patches, so I want to enable testing > with some SoC pin controllers as well and possibly make the > behavior default. > > Yours, > Linus Walleij >
Hi Linus On 5/24/19 1:24 PM, Linus Walleij wrote: > On Fri, May 10, 2019 at 9:42 AM Alexandre Torgue > <alexandre.torgue@st.com> wrote: > >> During power sequence, GPIO hardware registers could be lost if the power >> supply is switched off. Each device using pinctrl API is in charge of >> managing pins during suspend/resume sequences. But for pins used as gpio or >> irq stm32 pinctrl driver has to save the hardware configuration. >> Each register will be saved at runtime and restored during resume sequence. > > Both patches applied. > > On the same pinctrl devel branch is also Benjamin's patches to support > the "link_consumers" property on the pin controller descriptor to > enable links from pin control consumers back to their pin controller > suppliers, especially important for STMFX. > > Would you please check if it work fine if you turn on this feature > for the SoC STM32 pin controller? I just tested with Benjamin's patches and set "link_consumers" property for STM32 pinctrl. No changes on boot (except extra logs for each probe) and no changes on power tests too. regards alex > > I am working a bit on refining the patches, so I want to enable testing > with some SoC pin controllers as well and possibly make the > behavior default. > > Yours, > Linus Walleij >