All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 Ayan Kumar Halder <ayan.kumar.halder@xilinx.com>,
	Stefano Stabellini <stefanos@xilinx.com>
Subject: Re: [RFC PATCH 1/3] ARM: Introduce ARM_SINGLE_ARMV7R for ARMv7-R platforms
Date: Fri, 1 Jul 2022 13:24:37 +0200	[thread overview]
Message-ID: <CAK8P3a3A7Ay+fCyC0rKbnU3G9WsioJyrPEBVn3_vXij1NuyqCQ@mail.gmail.com> (raw)
In-Reply-To: <1fefdc0e-73c0-b6c9-83bf-2df9495d2f55@arm.com>

On Fri, Jul 1, 2022 at 11:22 AM Vladimir Murzin <vladimir.murzin@arm.com> wrote:
> On 6/30/22 10:22, Arnd Bergmann wrote:
> > On Thu, Jun 30, 2022 at 10:36 AM Vladimir Murzin
> >         ...
> >
> > That can of course be done independently from your series, but
> > it looks like ARM_SINGLE_ARMV7M and ARM_SINGLE_ARMV7R
> > are mostly the same here, except for the ARM_NVIC selects that
> > could be done by the platforms, and the CPU_V7/CPU_V7M
> > difference that could be folded into the CPU selection menu.
> >
>
> That sounds interesting! Moving NVIC into platforms looks straightforward,
> yet CPU selection would require some surgery:
>  - CPU_V7/CPU_V7M are not user selectable at the moment
>  - We still need some hint from the platform if it supports more
>    than one CPU variant, no?

Right, the two options still need to be visible somewhere. An obvious
place for this would be the CPU architecture select that currently
depends on ARCH_MULTIPLATFORM and contains the choice
between V4/v4TV5/V6/V6K/V7 but could be extended to cover
V7M and V7R, as well as possibly being extended to V7VE and
V8. I would also consider turning this into a 'choice' list where you
only pick the minimum CPU type, so e.g. enabling V6K lets you
pick V6K/V7/V7VE/V8 based machines but not
V4/V4T/V5/V6/V7M/V7R.

       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-01 11:32 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 [this message]
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
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=CAK8P3a3A7Ay+fCyC0rKbnU3G9WsioJyrPEBVn3_vXij1NuyqCQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.