mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Amelie Delaunay <amelie.delaunay@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Add STM32 SPI support on stm32mp157c
Date: Tue, 26 Jun 2018 15:01:18 +0200	[thread overview]
Message-ID: <3cad9448-3e19-b686-8f90-d9c2c9928450@st.com> (raw)
In-Reply-To: <1526566904-24514-1-git-send-email-amelie.delaunay@st.com>

Hi Amélie,

On 05/17/2018 04:21 PM, Amelie Delaunay wrote:
> This patch adds STM32 SPI support on stm32mp157c SoC.
> SPI1, available on GPIO expansion connector, is kept disabled, so these
> pins can be used as GPIOs by default.
> 
> Amelie Delaunay (3):
>    ARM: dts: stm32: add STM32 SPI support on stm32mp157c
>    ARM: dts: stm32: add SPI1 support on stm32mp157c-ev1
>    ARM: multi_v7_defconfig: enable STM32 SPI
> 
>   arch/arm/boot/dts/stm32mp157-pinctrl.dtsi | 16 +++++-
>   arch/arm/boot/dts/stm32mp157c-ev1.dts     |  6 +++
>   arch/arm/boot/dts/stm32mp157c.dtsi        | 84 +++++++++++++++++++++++++++++++
>   arch/arm/configs/multi_v7_defconfig       |  1 +
>   4 files changed, 106 insertions(+), 1 deletion(-)
> 

DT patches applied on stm32-next.

Thanks
Alex

      parent reply	other threads:[~2018-06-26 13:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 14:21 Amelie Delaunay
2018-05-17 14:21 ` [PATCH 1/3] ARM: dts: stm32: add " Amelie Delaunay
2018-05-17 14:21 ` [PATCH 2/3] ARM: dts: stm32: add SPI1 support on stm32mp157c-ev1 Amelie Delaunay
2018-05-17 14:21 ` [PATCH 3/3] ARM: multi_v7_defconfig: enable STM32 SPI Amelie Delaunay
2018-06-26  8:44   ` Alexandre Torgue
2018-06-26 11:47     ` Amelie DELAUNAY
2018-06-26 12:13       ` Alexandre Torgue
2018-06-26 13:01 ` 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=3cad9448-3e19-b686-8f90-d9c2c9928450@st.com \
    --to=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=arnd@arndb.de \
    --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®