public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Jessica Clarke <jrtc27@jrtc27.com>, Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Liviu Dudau <liviu.dudau@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v4 2/4] arm64: dts: morello: Add support for common functionalities
Date: Tue, 7 Jan 2025 14:34:38 +0000	[thread overview]
Message-ID: <bb0c95b6-760d-4de1-bc28-8f82e2fc5dd5@arm.com> (raw)
In-Reply-To: <Z30kbmA-3h-Rhg7l@Jessicas-MacBook-Pro>

Hi Jessica,

Thank you for your review.

On 07/01/2025 12:56, Jessica Clarke wrote:
> On Fri, Jan 03, 2025 at 04:14:31PM -0600, Rob Herring wrote:
>> On Fri, Jan 3, 2025 at 12:16 PM Vincenzo Frascino
>> <vincenzo.frascino@arm.com> wrote:
>>> +       cpus {
>>> +               #address-cells = <2>;
>>> +               #size-cells = <0>;
>>> +
>>> +               cpu0: cpu@0 {
>>> +                       compatible = "arm,neoverse-n1";
>>
>> I'm pretty sure the N1 doesn't support CHERI/morello. Perhaps
>> "arm,neoverse-n1-morello" if we want to capture what it is derived
>> from and since "arm,morello" is taken already.
> 
> Rainier is the codename of the core itself, and Morello LLVM recognises
> -mcpu=rainier not -mcpu=morello (there's -march=morello instead), so
> perhaps it should really be "arm,rainier". Though SMBIOS reports it as
> Morello-R0P1 so it may be best to use "arm,morello" here.
> 

We agree on the concept. It should either be "arm,rainier" or "arm,morello-r0p1"
if we want to capture the information of SMBIOS. When we reach consensus I will
update the patches accordingly (Please have a look at my reply to Rob).

> The real problem is that the board compatible has changed to include a
> generic "arm,morello" node, with the argument that a v2 board could
> appear. So why not instead change *that* to be something like:
> 
>   compatible = "arm,morello-sdp-v1", "arm,morello-sdp";
> 
> Then you can use "arm,morello" here for the cores.>

The name morello on its own is too overloaded of meaning if we do not specify to
what we are referring to.

> Though some of this may depend on what the FVP's DTS looks like; is it
> going to claim to be a Morello SDP, or does there need to be a common
> denominator compatible beneath that it can use?
> 

I still did not start bringing up to speed the DTS for FVP but I think that we
should distinguish in between SDP and FVP since not everything is the same,
hence it should have something similar to:

	compatible = "arm,morello-fvp", "arm,morello";

> Please CC me on future versions of this series.
> 

Will do.

> Jess

-- 
Regards,
Vincenzo


  reply	other threads:[~2025-01-07 14:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 18:16 [PATCH v4 0/4] arm64: dts: Add Arm Morello support Vincenzo Frascino
2025-01-03 18:16 ` [PATCH v4 1/4] dt-bindings: arm: Add Morello compatibility Vincenzo Frascino
2025-01-03 18:16 ` [PATCH v4 2/4] arm64: dts: morello: Add support for common functionalities Vincenzo Frascino
2025-01-03 22:14   ` Rob Herring
2025-01-07 12:56     ` Jessica Clarke
2025-01-07 14:34       ` Vincenzo Frascino [this message]
2025-01-07 14:51         ` Jessica Clarke
2025-01-07 14:56           ` Vincenzo Frascino
2025-01-07 14:17     ` Vincenzo Frascino
2025-01-03 22:26   ` Rob Herring
2025-01-07 14:41     ` Vincenzo Frascino
2025-01-07 12:44   ` Jessica Clarke
2025-01-07 14:49     ` Vincenzo Frascino
2025-01-03 18:16 ` [PATCH v4 3/4] arm64: dts: morello: Add support for soc dts Vincenzo Frascino
2025-01-03 18:16 ` [PATCH v4 4/4] MAINTAINERS: Add Vincenzo Frascino as Arm Morello Maintainer Vincenzo Frascino

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=bb0c95b6-760d-4de1-bc28-8f82e2fc5dd5@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jrtc27@jrtc27.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=liviu.dudau@arm.com \
    --cc=lpieralisi@kernel.org \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@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