mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: arinc9.unal@gmail.com
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	John Crispin <john@phrozen.org>
Cc: "Arınç ÜNAL" <arinc.unal@arinc9.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
	erkin.bozoglu@xeront.com
Subject: [PATCH 1/2] mips: remove SYS_HAS_CPU_MIPS32_R1 from RALINK
Date: Tue, 21 Feb 2023 12:24:34 +0300	[thread overview]
Message-ID: <20230221092435.22069-1-arinc.unal@arinc9.com> (raw)

From: Arınç ÜNAL <arinc.unal@arinc9.com>

All MIPS processors on the Ralink SoCs implement the MIPS32 Release 2
Architecture. Remove SYS_HAS_CPU_MIPS32_R1.

Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
---

The RT2880 SoC is MIPS 4KEc, the remaining SoCs are MIPS 24KEc. All of
which implement the MIPS32 Release 2 Architecture, if I understand
correctly. My incentive for this is to automatically have MIPS32R2 selected
as the CPU type.

---
 arch/mips/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 37072e15b263..0e8dab9a57de 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -610,7 +610,6 @@ config RALINK
 	select DMA_NONCOHERENT
 	select IRQ_MIPS_CPU
 	select USE_OF
-	select SYS_HAS_CPU_MIPS32_R1
 	select SYS_HAS_CPU_MIPS32_R2
 	select SYS_SUPPORTS_32BIT_KERNEL
 	select SYS_SUPPORTS_LITTLE_ENDIAN
-- 
2.37.2


             reply	other threads:[~2023-02-21  9:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  9:24 arinc9.unal [this message]
2023-02-21  9:24 ` [PATCH 2/2] mips: ralink: make SOC_MT7621 select PINCTRL arinc9.unal
2023-02-21  9:38   ` Sergio Paracuellos
2023-02-21 10:09     ` Arınç ÜNAL
2023-02-21 10:21       ` Sergio Paracuellos
2023-02-21 10:54         ` Arınç ÜNAL
2023-02-21 15:33           ` Sergio Paracuellos
2023-02-27 22:55   ` Thomas Bogendoerfer
2023-02-21 15:34 ` [PATCH 1/2] mips: remove SYS_HAS_CPU_MIPS32_R1 from RALINK Sergio Paracuellos
2023-02-27 22:55 ` Thomas Bogendoerfer

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=20230221092435.22069-1-arinc.unal@arinc9.com \
    --to=arinc9.unal@gmail.com \
    --cc=arinc.unal@arinc9.com \
    --cc=erkin.bozoglu@xeront.com \
    --cc=john@phrozen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=tsbogend@alpha.franken.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

all inboxes | Powered by JetHome®