From: Alexandre Torgue <alexandre.torgue@st.com>
To: Christophe Kerello <christophe.kerello@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<linux@armlinux.org.uk>, <olof@lixom.net>, <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] ARM: dts: stm32: add FMC2 NAND controller support on stm32mp157c
Date: Wed, 24 Jul 2019 18:38:05 +0200 [thread overview]
Message-ID: <4b6a8df1-593e-44b2-4bb3-2af9f732396c@st.com> (raw)
In-Reply-To: <1561128590-14621-2-git-send-email-christophe.kerello@st.com>
Hi Christophe
On 6/21/19 4:49 PM, Christophe Kerello wrote:
> This patch adds FMC2 NAND controller support used by stm32mp157c SOC.
>
> Signed-off-by: Christophe Kerello <christophe.kerello@st.com>
> ---
> arch/arm/boot/dts/stm32mp157c.dtsi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi b/arch/arm/boot/dts/stm32mp157c.dtsi
> index 0c4e6eb..f2bda28 100644
> --- a/arch/arm/boot/dts/stm32mp157c.dtsi
> +++ b/arch/arm/boot/dts/stm32mp157c.dtsi
> @@ -1239,6 +1239,25 @@
> dma-requests = <48>;
> };
>
> + fmc: nand-controller@58002000 {
> + compatible = "st,stm32mp15-fmc2";
> + reg = <0x58002000 0x1000>,
> + <0x80000000 0x1000>,
> + <0x88010000 0x1000>,
> + <0x88020000 0x1000>,
> + <0x81000000 0x1000>,
> + <0x89010000 0x1000>,
> + <0x89020000 0x1000>;
> + interrupts = <GIC_SPI 48 IRQ_TYPE_LEVEL_HIGH>;
> + dmas = <&mdma1 20 0x10 0x12000A02 0x0 0x0>,
> + <&mdma1 20 0x10 0x12000A08 0x0 0x0>,
> + <&mdma1 21 0x10 0x12000A0A 0x0 0x0>;
Please, don't use capital letter here.
> + dma-names = "tx", "rx", "ecc";
> + clocks = <&rcc FMC_K>;
> + resets = <&rcc FMC_R>;
> + status = "disabled";
> + };
> +
> qspi: spi@58003000 {
> compatible = "st,stm32f469-qspi";
> reg = <0x58003000 0x1000>, <0x70000000 0x10000000>;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-24 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 14:49 [PATCH 0/4] ARM: dts: stm32: enable FMC2 NAND controller on stm32mp157c-ev1 Christophe Kerello
2019-06-21 14:49 ` [PATCH 1/4] ARM: dts: stm32: add FMC2 NAND controller support on stm32mp157c Christophe Kerello
2019-07-24 16:38 ` Alexandre Torgue [this message]
2019-06-21 14:49 ` [PATCH 2/4] ARM: dts: stm32: add FMC2 NAND controller pins muxing on stm32mp157c-ev1 Christophe Kerello
2019-06-21 14:49 ` [PATCH 3/4] ARM: dts: stm32: enable FMC2 NAND controller " Christophe Kerello
2019-06-21 14:49 ` [PATCH 4/4] ARM: multi_v7_defconfig: add FMC2 NAND controller support Christophe Kerello
2019-07-25 10:20 ` [PATCH 0/4] ARM: dts: stm32: enable FMC2 NAND controller on stm32mp157c-ev1 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=4b6a8df1-593e-44b2-4bb3-2af9f732396c@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=christophe.kerello@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=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=olof@lixom.net \
--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).