public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: Joel Stanley <joel@jms•id.au>
Cc: Andrew Jeffery <andrew@aj•id.au>,
	linux-aspeed@lists•ozlabs.org,
	linux-arm-kernel@lists•infradead.org,
	Arnd Bergmann <arnd@arndb•de>,
	linux-kernel@vger•kernel.org
Subject: [PATCH] ARM: aspeed: ast2500 is ARMv6K
Date: Thu, 19 Sep 2019 16:26:38 +0200	[thread overview]
Message-ID: <20190919142654.1578823-1-arnd@arndb.de> (raw)

Linux supports both the original ARMv6 level (early ARM1136) and ARMv6K
(later ARM1136, ARM1176 and ARM11mpcore).

ast2500 falls into the second categoy, being based on arm1176jzf-s.
This is enabled by default when using ARCH_MULTI_V6, so we should
not 'select CPU_V6'.

Removing this will lead to more efficient use of atomic instructions.

Signed-off-by: Arnd Bergmann <arnd@arndb•de>
---
 arch/arm/mach-aspeed/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/arm/mach-aspeed/Kconfig b/arch/arm/mach-aspeed/Kconfig
index a293137f5814..163931a03136 100644
--- a/arch/arm/mach-aspeed/Kconfig
+++ b/arch/arm/mach-aspeed/Kconfig
@@ -26,7 +26,6 @@ config MACH_ASPEED_G4
 config MACH_ASPEED_G5
 	bool "Aspeed SoC 5th Generation"
 	depends on ARCH_MULTI_V6
-	select CPU_V6
 	select PINCTRL_ASPEED_G5 if !CC_IS_CLANG
 	select FTTMR010_TIMER
 	help
-- 
2.20.0


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

             reply	other threads:[~2019-09-19 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 14:26 Arnd Bergmann [this message]
2019-09-20  3:58 ` [PATCH] ARM: aspeed: ast2500 is ARMv6K Andrew Jeffery
2019-09-20  5:51 ` Joel Stanley
2019-09-20  7:42   ` Arnd Bergmann
2019-09-20  5:54 ` Andrew Jeffery

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=20190919142654.1578823-1-arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=andrew@aj$(echo .)id.au \
    --cc=joel@jms$(echo .)id.au \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-aspeed@lists$(echo .)ozlabs.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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