From: Alexandre Torgue <alexandre.torgue@st.com>
To: Amelie Delaunay <amelie.delaunay@st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: add SPI support on STM32H743 SoC
Date: Mon, 5 Mar 2018 09:42:48 +0100 [thread overview]
Message-ID: <f14b8e89-6487-1a1c-7f66-a0dcd3cd705b@st.com> (raw)
In-Reply-To: <1519814190-3208-1-git-send-email-amelie.delaunay@st.com>
Hi Amélie
On 02/28/2018 11:36 AM, Amelie Delaunay wrote:
> This patch adds all SPI instances of the STM32H743 SoC.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
> ---
Applied on stm32-next.
Thanks.
Alex
> arch/arm/boot/dts/stm32h743.dtsi | 61 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 61 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/arm/boot/dts/stm32h743.dtsi
> index 3a28cd2..2bb103e 100644
> --- a/arch/arm/boot/dts/stm32h743.dtsi
> +++ b/arch/arm/boot/dts/stm32h743.dtsi
> @@ -101,6 +101,27 @@
> };
> };
>
> + spi2: spi@40003800 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x40003800 0x400>;
> + interrupts = <36>;
> + clocks = <&rcc SPI2_CK>;
> + status = "disabled";
> +
> + };
> +
> + spi3: spi@40003c00 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x40003c00 0x400>;
> + interrupts = <51>;
> + clocks = <&rcc SPI3_CK>;
> + status = "disabled";
> + };
> +
> usart2: serial@40004400 {
> compatible = "st,stm32f7-uart";
> reg = <0x40004400 0x400>;
> @@ -141,6 +162,36 @@
> clocks = <&rcc USART1_CK>;
> };
>
> + spi1: spi@40013000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x40013000 0x400>;
> + interrupts = <35>;
> + clocks = <&rcc SPI1_CK>;
> + status = "disabled";
> + };
> +
> + spi4: spi@40013400 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x40013400 0x400>;
> + interrupts = <84>;
> + clocks = <&rcc SPI4_CK>;
> + status = "disabled";
> + };
> +
> + spi5: spi@40015000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x40015000 0x400>;
> + interrupts = <85>;
> + clocks = <&rcc SPI5_CK>;
> + status = "disabled";
> + };
> +
> dma1: dma@40020000 {
> compatible = "st,stm32-dma";
> reg = <0x40020000 0x400>;
> @@ -262,6 +313,16 @@
> reg = <0x58000400 0x400>;
> };
>
> + spi6: spi@58001400 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "st,stm32h7-spi";
> + reg = <0x58001400 0x400>;
> + interrupts = <86>;
> + clocks = <&rcc SPI6_CK>;
> + status = "disabled";
> + };
> +
> lptimer2: timer@58002400 {
> #address-cells = <1>;
> #size-cells = <0>;
>
prev parent reply other threads:[~2018-03-05 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 10:36 Amelie Delaunay
2018-03-05 8:42 ` 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=f14b8e89-6487-1a1c-7f66-a0dcd3cd705b@st.com \
--to=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.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
all inboxes | Powered by JetHome®