From: Alexandre Torgue <alexandre.torgue@st.com>
To: <patrice.chotard@st.com>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>,
Russell King <linux@armlinux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>, <soc@kernel.org>
Subject: Re: ARM: multi_v7_defconfig: Enable SPI_STM32_QSPI support
Date: Fri, 2 Aug 2019 09:38:04 +0200 [thread overview]
Message-ID: <d7e1c7d9-d905-1b37-159b-cc3d981af8da@st.com> (raw)
In-Reply-To: <20190731072204.32160-1-patrice.chotard@st.com>
Dear Patrice
On 7/31/19 9:22 AM, patrice.chotard@st.com wrote:
> From: Patrice Chotard <patrice.chotard@st.com>
>
> Enable support for QSPI block on STM32 SoCs.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
> ---
> arch/arm/configs/multi_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 6a40bc2ef271..78d1d93298af 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -403,6 +403,7 @@ CONFIG_SPI_SH_MSIOF=m
> CONFIG_SPI_SH_HSPI=y
> CONFIG_SPI_SIRF=y
> CONFIG_SPI_STM32=m
> +CONFIG_SPI_STM32_QSPI=m
> CONFIG_SPI_SUN4I=y
> CONFIG_SPI_SUN6I=y
> CONFIG_SPI_TEGRA114=y
>
Applied on stm32-next.
Thanks.
Alex
next prev parent reply other threads:[~2019-08-02 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 7:22 ARM: multi_v7_defconfig: Enable SPI_STM32_QSPI support patrice.chotard
2019-08-02 7:38 ` Alexandre Torgue [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-29 13:55 patrice.chotard
2019-07-30 17:36 ` Olof Johansson
2019-07-31 6:47 ` Alexandre Torgue
2019-07-31 13:20 ` Olof Johansson
2019-07-31 13:21 ` Olof Johansson
2019-07-31 14:40 ` Alexandre Torgue
2019-07-31 7:15 ` Patrice CHOTARD
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=d7e1c7d9-d905-1b37-159b-cc3d981af8da@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--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=olof@lixom.net \
--cc=patrice.chotard@st.com \
--cc=soc@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).