From: Marek Vasut <marex@denx.de>
To: patrice.chotard@foss.st.com, robh+dt@kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
alexandre.torgue@foss.st.com
Cc: mcoquelin.stm32@gmail.com,
linux-stm32@st-md-mailman.stormreply.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: [PATCH 2/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp15xx-dhcom-som
Date: Mon, 12 Dec 2022 14:01:10 +0100 [thread overview]
Message-ID: <2b5d33a1-4f8d-e1db-67ef-7e5c32d1ee83@denx.de> (raw)
In-Reply-To: <20221212085142.3944367-3-patrice.chotard@foss.st.com>
On 12/12/22 09:51, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> Chip select pinctrl phandle was missing in several stm32mp15x based boards.
>
> Fixes: ea99a5a02ebc ("ARM: dts: stm32: Create separate pinmux for qspi cs pin in stm32mp15-pinctrl.dtsi)
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Alexandre Torgue <alexandre.torgue@st.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> To: linux-arm-kernel@lists.infradead.org
> ---
> arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> index 238a611192e7..d3b85a8764d7 100644
> --- a/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp15xx-dhcom-som.dtsi
> @@ -428,8 +428,12 @@ &pwr_regulators {
>
> &qspi {
> pinctrl-names = "default", "sleep";
> - pinctrl-0 = <&qspi_clk_pins_a &qspi_bk1_pins_a>;
> - pinctrl-1 = <&qspi_clk_sleep_pins_a &qspi_bk1_sleep_pins_a>;
> + pinctrl-0 = <&qspi_clk_pins_a
> + &qspi_bk1_pins_a
> + &qspi_cs1_pins_a>;
> + pinctrl-1 = <&qspi_clk_sleep_pins_a
> + &qspi_bk1_sleep_pins_a
> + &qspi_cs1_sleep_pins_a>;
> reg = <0x58003000 0x1000>, <0x70000000 0x4000000>;
> #address-cells = <1>;
> #size-cells = <0>;
Splitting the pins makes sense indeed.
Reviewed-by: Marek Vasut <marex@denx.de>
next prev parent reply other threads:[~2022-12-12 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 8:51 [PATCH 0/4] Fix qspi pinctrl phandle for stm3mp15 based boards patrice.chotard
2022-12-12 8:51 ` [PATCH 1/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp15xx-dhcor-som patrice.chotard
2022-12-12 13:01 ` Marek Vasut
2022-12-12 8:51 ` [PATCH 2/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp15xx-dhcom-som patrice.chotard
2022-12-12 13:01 ` Marek Vasut [this message]
2022-12-12 8:51 ` [PATCH 3/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp157c-emstamp-argon patrice.chotard
2022-12-12 8:51 ` [PATCH 4/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp151a-prtt1l patrice.chotard
2022-12-12 12:59 ` [PATCH 0/4] Fix qspi pinctrl phandle for stm3mp15 based boards Marek Vasut
2023-01-09 16:26 ` 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:
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=2b5d33a1-4f8d-e1db-67ef-7e5c32d1ee83@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@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).