linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	 Ayan Kumar Halder <ayan.kumar.halder@xilinx.com>,
	Stefano Stabellini <stefanos@xilinx.com>
Subject: Re: [RFC PATCH 0/3] ARM: Support Cortex-R platform(s)
Date: Tue, 12 Jul 2022 11:23:30 +0200	[thread overview]
Message-ID: <CAK8P3a35dhppbkPPEwDMHU0S3Gxr0+M3fVpja1QhJh7+HGs+Sw@mail.gmail.com> (raw)
In-Reply-To: <a5d95d77-ea86-b4de-2995-3dac90664801@arm.com>

On Tue, Jul 12, 2022 at 10:33 AM Vladimir Murzin
<vladimir.murzin@arm.com> wrote:
> On 6/30/22 09:36, Vladimir Murzin wrote:
> >
> > I've been running Linux on Cortex-R cores with downstream patches for
> > several years already. There are few reasons why we have not got any
> > real platform supporting Cortex-R cores so far:
> > 1) lack of interest
> > 2) lack of easily available platforms
> > 3) missing Kconfig bits
> >
> > During these years I've been receiving questions (mostly in private)
> > about running Linux with Cortex-R cores. Use cases vary, but mostly
> > fall under "we know Linux and do not want yet another RTOS", also
> > people not always care about real-time features of R-class cores and
> > see it as an upgrade from M-class cores.
> >
> > Sometime ago MPS3 platform got support for FPGA image [1] with
> > Cortex-R52 cores where Linux can live comfortably.
> >
> > This patchset addresses #3 and brings support for MPS3 platform
> > featuring Cortex-R52
> >
> > [1] https://developer.arm.com/downloads/-/download-fpga-images
>
> Anything I can do to make progress with the series or it falls under
> "we do not care" category?

I think at this point it's an actively bad idea to merge support for Cortex-R.

I don't think anyone else cares, but if you can find other people that want
this to get merged (and know what they are talking about), you can
overrule me on this.

The existing MPS2 support is important because it gives developers
an easy way to test Cortex-M based NOMMU code, and we still have
users on STM32 at least. I do expect the STM32 MCU user base to
further shrink, to the point where nobody is updating their kernels any
more and we want to remove not just STM32 but all other Cortex-M
platforms. All others are already further down the road of decline and
MPS2 is not useful by itself.

Merging MPS3/Cortex-R52 now feels like a step in the wrong
direction, if that leads to a future situation where we remove
Cortex-M but keep Cortex-R support around.

        Arnd

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

  reply	other threads:[~2022-07-12  9:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30  8:36 [RFC PATCH 0/3] ARM: Support Cortex-R platform(s) Vladimir Murzin
2022-06-30  8:36 ` [RFC PATCH 1/3] ARM: Introduce ARM_SINGLE_ARMV7R for ARMv7-R platforms Vladimir Murzin
2022-06-30  9:22   ` Arnd Bergmann
2022-07-01  9:22     ` Vladimir Murzin
2022-07-01 11:24       ` Arnd Bergmann
2022-06-30  8:36 ` [RFC PATCH 2/3] ARM: mps2: Split into ARCH/MACH options Vladimir Murzin
2022-06-30  8:36 ` [RFC PATCH 3/3] ARM: Introduce MPS3 AN536 Vladimir Murzin
2022-06-30 20:36   ` Stefano Stabellini
2022-07-01  9:06     ` Vladimir Murzin
2022-06-30 21:17 ` [RFC PATCH 0/3] ARM: Support Cortex-R platform(s) Arnd Bergmann
2022-07-01  9:39   ` Vladimir Murzin
2022-07-01 14:18     ` Arnd Bergmann
2022-07-01 14:38       ` Vladimir Murzin
2022-07-12  8:33 ` Vladimir Murzin
2022-07-12  9:23   ` Arnd Bergmann [this message]
2022-07-12 20:44     ` Stefano Stabellini
2022-08-01 15:11       ` 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=CAK8P3a35dhppbkPPEwDMHU0S3Gxr0+M3fVpja1QhJh7+HGs+Sw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=ayan.kumar.halder@xilinx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stefanos@xilinx.com \
    --cc=vladimir.murzin@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).