From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>,
Marek Vasut <marex@denx.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 1/1] ARM: dts: stm32: fix AV96 board SAI2 pin muxing on stm32mp15
Date: Mon, 7 Feb 2022 11:54:44 +0100 [thread overview]
Message-ID: <38a9ce0a-b63e-8321-bd85-c42638f31d39@foss.st.com> (raw)
In-Reply-To: <20220124153525.17314-1-olivier.moysan@foss.st.com>
Hi Olivier
On 1/24/22 16:35, Olivier Moysan wrote:
> Replace sai2a-2 node name by sai2a-sleep-2, to avoid name
> duplication.
>
> Fixes: 1a9a9d226f0f ("ARM: dts: stm32: fix AV96 board SAI2 pin muxing on stm32mp15")
>
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
> ---
> arch/arm/boot/dts/stm32mp15-pinctrl.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> index 3b65130affec..6161f5906ec1 100644
> --- a/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15-pinctrl.dtsi
> @@ -1190,7 +1190,7 @@
> };
> };
>
> - sai2a_sleep_pins_c: sai2a-2 {
> + sai2a_sleep_pins_c: sai2a-sleep-2 {
> pins {
> pinmux = <STM32_PINMUX('D', 13, ANALOG)>, /* SAI2_SCK_A */
> <STM32_PINMUX('D', 11, ANALOG)>, /* SAI2_SD_A */
Applied on stm32-next.
Thanks
Alex
prev parent reply other threads:[~2022-02-07 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:35 [PATCH 1/1] ARM: dts: stm32: fix AV96 board SAI2 pin muxing on stm32mp15 Olivier Moysan
2022-02-07 10:54 ` Alexandre TORGUE [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=38a9ce0a-b63e-8321-bd85-c42638f31d39@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).