From: ludovic.barre@st.com (Ludovic BARRE)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/9] ARM: stm32: prepare stm32 family to welcome armv7 architecture
Date: Tue, 19 Dec 2017 15:43:02 +0100 [thread overview]
Message-ID: <45e2f530-1e72-6933-4367-95aadd709873@st.com> (raw)
In-Reply-To: <CAK8P3a1WzkVQ3591XjVQPLCqP0_zZ4ksqJqWvm7de_OnkE3oaQ@mail.gmail.com>
On 12/18/2017 09:24 PM, Arnd Bergmann wrote:
> On Mon, Dec 18, 2017 at 4:17 PM, Ludovic Barre <ludovic.Barre@st.com> wrote:
>> From: Ludovic Barre <ludovic.barre@st.com>
>>
>> This patch prepares the STM32 machine for the integration of Cortex-A
>> based microprocessor (MPU), on top of the existing Cortex-M
>> microcontroller family (MCU). Since both MCUs and MPUs are sharing
>> common hardware blocks we can keep using ARCH_STM32 flag for most of
>> them. If a hardware block is specific to one family we can use either
>> ARM_SINGLE_ARMV7M or ARCH_MULTI_V7 flag.
>>
>> Signed-off-by: Ludovic Barre <ludovic.barre@st.com>
>
> Looks good overall. Two more small comments:
>
>
>>
>> +if ARCH_STM32
>> +
>> config MACH_STM32F429
>> - bool "STMicrolectronics STM32F429"
>> - depends on ARCH_STM32
>> + bool "STMicroelectronics STM32F429"
>> + depends on ARM_SINGLE_ARMV7M
>> default y
>
> Instead of the explicit dependency for each board, I'd leave the surrounding
> 'if ARM_SINGLE_ARMV7M'. I think you had in v1.
As you suggest, I follow mach-at91 example.
The point is on "depends on ARM_SINGLE_ARMV7M" ?
You prefer this way:
config MACH_STM32F429
bool "STMicroelectronics STM32F429" if ARM_SINGLE_ARMV7M
default y
BR
Ludo
>
>> diff --git a/arch/arm/mach-stm32/Makefile b/arch/arm/mach-stm32/Makefile
>> index bd0b7b5..5940af1 100644
>> --- a/arch/arm/mach-stm32/Makefile
>> +++ b/arch/arm/mach-stm32/Makefile
>> @@ -1 +1 @@
>> -obj-y += board-dt.o
>> +obj-$(CONFIG_ARM_SINGLE_ARMV7M) += board-mcu-dt.o
>> diff --git a/arch/arm/mach-stm32/board-dt.c b/arch/arm/mach-stm32/board-mcu-dt.c
>> similarity index 100%
>> rename from arch/arm/mach-stm32/board-dt.c
>> rename to arch/arm/mach-stm32/board-mcu-dt.c
>
> Why the rename? I don't expect the new machines to have any notable
> contents in a board file, if any at all, so just use one file for both.
> I see the board-dt.c file refers to armv7m_restart, we can either put
> that in an #ifdef, or find a way to make it the default for all armv7-m
> platforms that don't provide any other restart method.
>
> Arnd
>
next prev parent reply other threads:[~2017-12-19 14:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:17 [PATCH V2 0/9] ARM: stm32: add initial STM32MPU support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 1/9] devicetree: bindings: Document supported STM32 SoC family Ludovic Barre
2017-12-20 7:33 ` Linus Walleij
2017-12-18 15:17 ` [PATCH V2 2/9] Documentation: arm: stm32: move to rst format Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 3/9] ARM: stm32: prepare stm32 family to welcome armv7 architecture Ludovic Barre
2017-12-18 20:24 ` Arnd Bergmann
2017-12-19 14:38 ` Alexandre Torgue
2017-12-21 16:39 ` Ludovic BARRE
2017-12-21 20:48 ` Arnd Bergmann
2017-12-19 14:43 ` Ludovic BARRE [this message]
2017-12-19 15:26 ` Arnd Bergmann
2017-12-19 15:54 ` Ludovic BARRE
2017-12-18 15:17 ` [PATCH V2 4/9] devicetree: bindings: stm32: add support of STM32MP157 Ludovic Barre
2017-12-20 18:24 ` Rob Herring
2017-12-18 15:17 ` [PATCH V2 5/9] ARM: stm32: add initial support for STM32MP157 Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 6/9] pinctrl: stm32: Add STM32MP157 MPU support Ludovic Barre
2017-12-20 7:38 ` Linus Walleij
2017-12-18 15:17 ` [PATCH V2 7/9] ARM: configs: multi_v7: add stm32 support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 8/9] ARM: dts: stm32: add stm32mp157c initial support Ludovic Barre
2017-12-18 15:17 ` [PATCH V2 9/9] ARM: dts: stm32: add initial support of stm32mp157c eval board Ludovic Barre
2017-12-18 20:20 ` Arnd Bergmann
2017-12-19 8:45 ` Ludovic BARRE
2017-12-19 9:17 ` Alexandre Torgue
2017-12-20 7:44 ` Linus Walleij
2017-12-20 9:19 ` Alexandre Torgue
2017-12-21 9:18 ` Linus Walleij
2017-12-21 10:44 ` 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=45e2f530-1e72-6933-4367-95aadd709873@st.com \
--to=ludovic.barre@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