public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: "Russell King" <linux@armlinux.org.uk>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	"Ard Biesheuvel" <ardb@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Anshuman Khandual" <anshuman.khandual@arm.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Mike Rapoport" <rppt@kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] ARM: Kconfig: improve ARM_SINGLE_ARMV7M description with Cortex M7
Date: Fri, 3 Dec 2021 09:30:39 +0000	[thread overview]
Message-ID: <db427a15-231b-957e-3690-73373fec55ea@arm.com> (raw)
In-Reply-To: <20211202222002.33456-1-giulio.benetti@benettiengineering.com>

On 12/2/21 10:20 PM, Giulio Benetti wrote:
> ARM_SINGLE_ARMV7M implies Arm Cortex M7 too, so let's add it to
> description with M0/M3/M4.

Well it also implies M33 and M55. I'd suggest drop specific implementations
from description - so we do not need to update it each time new compatible
core is released. To account newest cores like M33 and M55 you can rephrase
to:
- ARMv7-M/v8-M
- ARMv7-M and above

Cheers
Vladimir

> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  arch/arm/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index c2724d986fa0..67efbde70e34 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -329,7 +329,7 @@ config ARCH_MULTIPLATFORM
>  	select USE_OF
>  
>  config ARM_SINGLE_ARMV7M
> -	bool "ARMv7-M based platforms (Cortex-M0/M3/M4)"
> +	bool "ARMv7-M based platforms (Cortex-M0/M3/M4/M7)"
>  	depends on !MMU
>  	select ARM_NVIC
>  	select AUTO_ZRELADDR
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-03  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 22:20 [PATCH] ARM: Kconfig: improve ARM_SINGLE_ARMV7M description with Cortex M7 Giulio Benetti
2021-12-03  9:30 ` Vladimir Murzin [this message]
2021-12-03 16:41   ` Giulio Benetti
2021-12-03 17:01     ` Vladimir Murzin
2021-12-03 17:03       ` Giulio Benetti
2021-12-03 17:09       ` [PATCH] ARM: Kconfig: improve ARM_SINGLE_ARMV7M with ARMv8-M too Giulio Benetti
2021-12-03 17:12         ` Vladimir Murzin

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=db427a15-231b-957e-3690-73373fec55ea@arm.com \
    --to=vladimir.murzin@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=geert+renesas@glider.be \
    --cc=giulio.benetti@benettiengineering.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=lukas.bulwahn@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rppt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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