From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Christophe Kerello <christophe.kerello@foss.st.com>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.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 v2] ARM: dts: stm32: add FMC support on STM32MP13x SoC family
Date: Mon, 3 Apr 2023 10:20:50 +0200 [thread overview]
Message-ID: <fa36c2bc-c617-014e-fb11-d7621be866a0@foss.st.com> (raw)
In-Reply-To: <20230328170711.247745-1-christophe.kerello@foss.st.com>
Hi christophe
On 3/28/23 19:07, Christophe Kerello wrote:
> Add FMC support on STM32MP13x SoC family.
>
> Signed-off-by: Christophe Kerello <christophe.kerello@foss.st.com>
> ---
Applied on stm32-next.
Thanks.
Alex
> Changes in v2:
> - compatible, reg and ranges properties have been moved at the top of each node
>
> arch/arm/boot/dts/stm32mp131.dtsi | 33 +++++++++++++++++++++++++++++++
> 1 file changed, 33 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp131.dtsi b/arch/arm/boot/dts/stm32mp131.dtsi
> index 9ea61687f023..7ea1fe0cd070 100644
> --- a/arch/arm/boot/dts/stm32mp131.dtsi
> +++ b/arch/arm/boot/dts/stm32mp131.dtsi
> @@ -1232,6 +1232,39 @@ mdma: dma-controller@58000000 {
> dma-requests = <48>;
> };
>
> + fmc: memory-controller@58002000 {
> + compatible = "st,stm32mp1-fmc2-ebi";
> + reg = <0x58002000 0x1000>;
> + ranges = <0 0 0x60000000 0x04000000>, /* EBI CS 1 */
> + <1 0 0x64000000 0x04000000>, /* EBI CS 2 */
> + <2 0 0x68000000 0x04000000>, /* EBI CS 3 */
> + <3 0 0x6c000000 0x04000000>, /* EBI CS 4 */
> + <4 0 0x80000000 0x10000000>; /* NAND */
> + #address-cells = <2>;
> + #size-cells = <1>;
> + clocks = <&rcc FMC_K>;
> + resets = <&rcc FMC_R>;
> + status = "disabled";
> +
> + nand-controller@4,0 {
> + compatible = "st,stm32mp1-fmc2-nfc";
> + reg = <4 0x00000000 0x1000>,
> + <4 0x08010000 0x1000>,
> + <4 0x08020000 0x1000>,
> + <4 0x01000000 0x1000>,
> + <4 0x09010000 0x1000>,
> + <4 0x09020000 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + interrupts = <GIC_SPI 49 IRQ_TYPE_LEVEL_HIGH>;
> + dmas = <&mdma 24 0x2 0x12000a02 0x0 0x0>,
> + <&mdma 24 0x2 0x12000a08 0x0 0x0>,
> + <&mdma 25 0x2 0x12000a0a 0x0 0x0>;
> + dma-names = "tx", "rx", "ecc";
> + status = "disabled";
> + };
> + };
> +
> sdmmc1: mmc@58005000 {
> compatible = "st,stm32-sdmmc2", "arm,pl18x", "arm,primecell";
> arm,primecell-periphid = <0x20253180>;
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-04-03 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 17:07 [PATCH v2] ARM: dts: stm32: add FMC support on STM32MP13x SoC family Christophe Kerello
2023-04-03 8:20 ` 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=fa36c2bc-c617-014e-fb11-d7621be866a0@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=christophe.kerello@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=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).