LKML Archive on
help / color / mirror / Atom feed
From: Linus Walleij <>
To: Alexandre Torgue <>,
	Benjamin Gaignard <>
Cc: Maxime Coquelin <>,
	"" <>,
	"open list:GPIO SUBSYSTEM" <>,
	Linux ARM <>,
Subject: Re: [PATCH 0/2] pinctrl: stm32: add suspend/resume management
Date: Fri, 24 May 2019 13:24:37 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, May 10, 2019 at 9:42 AM Alexandre Torgue
<> 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.

Linus Walleij

  parent reply	other threads:[~2019-05-24 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10  7:42 Alexandre Torgue
2019-05-10  7:42 ` [PATCH 1/2] " Alexandre Torgue
2019-05-10  7:42 ` [PATCH 2/2] pinctrl: stm32: Enable suspend/resume for stm32mp157c SoC Alexandre Torgue
2019-05-24 11:24 ` Linus Walleij [this message]
2019-05-24 12:26   ` [PATCH 0/2] pinctrl: stm32: add suspend/resume management Alexandre Torgue
2019-05-27 16:17   ` Alexandre Torgue

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 0/2] pinctrl: stm32: add suspend/resume management' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).