From: Ludovic BARRE <ludovic.barre@st.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King <linux@armlinux.org.uk>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Gerald Baeza <gerald.baeza@st.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>
Subject: Re: [PATCH V2 3/9] ARM: stm32: prepare stm32 family to welcome armv7 architecture
Date: Tue, 19 Dec 2017 16:54:57 +0100 [thread overview]
Message-ID: <00e3d1b3-56cc-f003-9538-0cc769a00c9c@st.com> (raw)
In-Reply-To: <CAK8P3a3X1icDWmVng8w0Yd58nAcViJQ9oZc4xm-dEycVPe+5pg@mail.gmail.com>
On 12/19/2017 04:26 PM, Arnd Bergmann wrote:
> On Tue, Dec 19, 2017 at 3:43 PM, Ludovic BARRE <ludovic.barre@st.com> wrote:
>>
>>
>> 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
>>
>
> No, that would be wrong, that way you would always enable
> MACH_STM32F429 when ARM_SINGLE_ARMV7M is turned
> off, which is exactly the wrong way round. What I meant is
>
> if ARCH_STM32
>
> if ARM_SINGLE_ARMV7M
>
> config MACH_STM32F429
> bool "STMicrolectronics STM32F429"
>
> config MACH_STM32...
> ...
>
> endif # ARMv7-M
>
> if ARCH_MULTI_V7
>
> config MACH_STM32...
> ...
>
> endif # ARMv7-A
>
> endif # STM32
>
> Arnd
>
Ok, it's clear :-)
next prev parent reply other threads:[~2017-12-19 15:56 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
2017-12-19 15:26 ` Arnd Bergmann
2017-12-19 15:54 ` Ludovic BARRE [this message]
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=00e3d1b3-56cc-f003-9538-0cc769a00c9c@st.com \
--to=ludovic.barre@st.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gerald.baeza@st.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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®