From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Christian Bruel <christian.bruel@foss.st.com>,
corbet@lwn.net, bhelgaas@google.com, mani@kernel.org,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Add pinctrl_pm_select_init_state helper function
Date: Mon, 18 Aug 2025 18:06:59 -0500 [thread overview]
Message-ID: <20250818230659.GA561724@bhelgaas> (raw)
In-Reply-To: <CACRpkdZGaMf1m9UK7ai3KLJBSJtWJagzMMa6icMxEL04w7fkMA@mail.gmail.com>
On Mon, Aug 18, 2025 at 05:32:14PM +0200, Linus Walleij wrote:
> On Wed, Aug 13, 2025 at 10:13 AM Christian Bruel
> <christian.bruel@foss.st.com> wrote:
>
> > Some platforms need to set the pinctrl to an initial state during
> > pm_resume, just like during probe. To achieve this, the missing function
> > pinctrl_pm_select_init_state() is added to the list of already existing
> > pinctrl PM helper functions.
> >
> > This allows a driver to use the pinctrl init and default states in the
> > pm_runtime platform resume handlers, just as in probe.
> >
> > Additionally the missing documentation describing these pinctrl standard
> > states used during probe has been added.
> >
> > This fixes a build issue for the STM32MP25 PCIe staged in the pcie tree,
> > id 5a972a01e24b
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Björn: Just apply this to the PCI tree.
Thanks, Linus, will do!
Bjorn
prev parent reply other threads:[~2025-08-18 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:11 [PATCH v1 0/2] Add pinctrl_pm_select_init_state helper function Christian Bruel
2025-08-13 8:11 ` [PATCH v1 1/2] Documentation: pinctrl: Describe PM helper functions for standard states Christian Bruel
2025-08-18 15:31 ` Linus Walleij
2025-08-13 8:11 ` [PATCH v1 2/2] pinctrl: Add pinctrl_pm_select_init_state helper function Christian Bruel
2025-08-18 15:31 ` Linus Walleij
2025-08-18 15:32 ` [PATCH v1 0/2] " Linus Walleij
2025-08-18 23:06 ` Bjorn Helgaas [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250818230659.GA561724@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=christian.bruel@foss.st.com \
--cc=corbet@lwn.net \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox