From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: multi_v7_defconfig: enable STM32 SPI
Date: Tue, 26 Jun 2018 10:44:32 +0200 [thread overview]
Message-ID: <e3bd3097-fbde-b790-e2b3-d78fb34b849d@st.com> (raw)
In-Reply-To: <1526566904-24514-4-git-send-email-amelie.delaunay@st.com>
Hi Am?lie
On 05/17/2018 04:21 PM, Amelie Delaunay wrote:
> Enable the STM32 SPI driver, implemented on STM32MP1 SoC.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@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 89167cd..f990335 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -411,6 +411,7 @@ CONFIG_SPI_S3C64XX=m
> CONFIG_SPI_SH_MSIOF=m
> CONFIG_SPI_SH_HSPI=y
> CONFIG_SPI_SIRF=y
> +CONFIG_SPI_STM32=y
> CONFIG_SPI_SUN4I=y
> CONFIG_SPI_SUN6I=y
> CONFIG_SPI_TEGRA114=y
>
Driver which are are not "vital" to boot STM32 platform should be
defined as module. It's the case for this one. Isn't ?
Regards
Alex
next prev parent reply other threads:[~2018-06-26 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 14:21 [PATCH 0/3] Add STM32 SPI support on stm32mp157c 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 [this message]
2018-06-26 11:47 ` Amelie DELAUNAY
2018-06-26 12:13 ` Alexandre Torgue
2018-06-26 13:01 ` [PATCH 0/3] Add STM32 SPI support on stm32mp157c 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=e3bd3097-fbde-b790-e2b3-d78fb34b849d@st.com \
--to=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.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