From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: <patrice.chotard@foss.st.com>, <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: Add QSPI support on STM32MP13x SoC family
Date: Mon, 3 Apr 2023 11:23:16 +0200 [thread overview]
Message-ID: <f4721c8a-d4f0-d391-b9c9-d1a8cf5538b4@foss.st.com> (raw)
In-Reply-To: <20230331071907.4127388-1-patrice.chotard@foss.st.com>
hi Patrice
On 3/31/23 09:19, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> Add QSPI support on STM32MP13x SoC family
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
> arch/arm/boot/dts/stm32mp131.dtsi | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp131.dtsi b/arch/arm/boot/dts/stm32mp131.dtsi
> index 5949473cbbfd..544c755b6e67 100644
> --- a/arch/arm/boot/dts/stm32mp131.dtsi
> +++ b/arch/arm/boot/dts/stm32mp131.dtsi
> @@ -1137,6 +1137,21 @@ mdma: dma-controller@58000000 {
> dma-requests = <48>;
> };
>
> + qspi: spi@58003000 {
> + compatible = "st,stm32f469-qspi";
> + reg = <0x58003000 0x1000>, <0x70000000 0x10000000>;
> + reg-names = "qspi", "qspi_mm";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>;
> + dmas = <&mdma 26 0x2 0x10100002 0x0 0x0>,
> + <&mdma 26 0x2 0x10100008 0x0 0x0>;
> + dma-names = "tx", "rx";
> + clocks = <&rcc QSPI_K>;
> + resets = <&rcc QSPI_R>;
> + status = "disabled";
> + };
> +
> sdmmc1: mmc@58005000 {
> compatible = "st,stm32-sdmmc2", "arm,pl18x", "arm,primecell";
> arm,primecell-periphid = <0x20253180>;
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2023-04-03 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 7:19 [PATCH] ARM: dts: stm32: Add QSPI support on STM32MP13x SoC family patrice.chotard
2023-04-03 9:23 ` 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=f4721c8a-d4f0-d391-b9c9-d1a8cf5538b4@foss.st.com \
--to=alexandre.torgue@foss.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=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).