All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Alexandre Courbot
	<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] arm64: tegra: Fix CPU compatible string for Tegra132
Date: Wed, 25 May 2016 09:42:28 -0600	[thread overview]
Message-ID: <5745C7E4.2050908@wwwdotorg.org> (raw)
In-Reply-To: <574509E7.4030208-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 05/24/2016 08:11 PM, Joseph Lo wrote:
> On 05/23/2016 03:42 PM, Joseph Lo wrote:
>> As per commit f634da375fc96 ("Documentation: DT bindings: add nvidia,
>> tegra132-denver compatible string"), fixing the CPU compatible string for
>> Tegra132 to match the binding document currently.
>>
>> Signed-off-by: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>> ---
>>   arch/arm64/boot/dts/nvidia/tegra132.dtsi | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> index 2013f8916084..7b1cdc029de3 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> @@ -964,13 +964,13 @@
>>
>>           cpu@0 {
>>               device_type = "cpu";
>> -            compatible = "nvidia,denver", "arm,armv8";
>> +            compatible = "nvidia,tegra132-denver", "arm,armv8";
>
> Hi Stephen, Thierry,
>
> Should we fix this or fix the compatible string in the binding document
> as just "nvidia,denver" to represent all the Devner CPU revisions just
> like some other CPUs did? e.g. arm,cortex-a57, which represents all the
> A57 revisions.

I would expect compatible to be:

compatible = "nvidia,tegra132-denver", "nvidia,denver", "arm,armv8";

The "nvidia,denver" entry is already present, and hence probably 
shouldn't be removed. It can represent "Denver 1.0". We should add the 
T132 entry to indicate the specific implementation. Admittedly right now 
there's a 1:1 relation between SoC and Denver version. Either/both of 
those could in theory be required to trigger specific bug-fixes/WARs.

For later chips which have a different Denver version, I'd expect to see 
something like:

compatible = "nvidia,tegraNNN-denver", "nvidia,denverMMM", "arm,armv8";

... where NNN is the SoC version/name and MMM is the Denver version. 
There could be extra entries in the property if the new versions are 
backwards-compatible with old versions.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: tegra: Fix CPU compatible string for Tegra132
Date: Wed, 25 May 2016 09:42:28 -0600	[thread overview]
Message-ID: <5745C7E4.2050908@wwwdotorg.org> (raw)
In-Reply-To: <574509E7.4030208@nvidia.com>

On 05/24/2016 08:11 PM, Joseph Lo wrote:
> On 05/23/2016 03:42 PM, Joseph Lo wrote:
>> As per commit f634da375fc96 ("Documentation: DT bindings: add nvidia,
>> tegra132-denver compatible string"), fixing the CPU compatible string for
>> Tegra132 to match the binding document currently.
>>
>> Signed-off-by: Joseph Lo <josephl@nvidia.com>
>> ---
>>   arch/arm64/boot/dts/nvidia/tegra132.dtsi | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> index 2013f8916084..7b1cdc029de3 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
>> @@ -964,13 +964,13 @@
>>
>>           cpu at 0 {
>>               device_type = "cpu";
>> -            compatible = "nvidia,denver", "arm,armv8";
>> +            compatible = "nvidia,tegra132-denver", "arm,armv8";
>
> Hi Stephen, Thierry,
>
> Should we fix this or fix the compatible string in the binding document
> as just "nvidia,denver" to represent all the Devner CPU revisions just
> like some other CPUs did? e.g. arm,cortex-a57, which represents all the
> A57 revisions.

I would expect compatible to be:

compatible = "nvidia,tegra132-denver", "nvidia,denver", "arm,armv8";

The "nvidia,denver" entry is already present, and hence probably 
shouldn't be removed. It can represent "Denver 1.0". We should add the 
T132 entry to indicate the specific implementation. Admittedly right now 
there's a 1:1 relation between SoC and Denver version. Either/both of 
those could in theory be required to trigger specific bug-fixes/WARs.

For later chips which have a different Denver version, I'd expect to see 
something like:

compatible = "nvidia,tegraNNN-denver", "nvidia,denverMMM", "arm,armv8";

... where NNN is the SoC version/name and MMM is the Denver version. 
There could be extra entries in the property if the new versions are 
backwards-compatible with old versions.

  parent reply	other threads:[~2016-05-25 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  7:42 [PATCH] arm64: tegra: Fix CPU compatible string for Tegra132 Joseph Lo
2016-05-23  7:42 ` Joseph Lo
     [not found] ` <20160523074221.7135-1-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-25  2:11   ` Joseph Lo
2016-05-25  2:11     ` Joseph Lo
     [not found]     ` <574509E7.4030208-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-25 15:42       ` Stephen Warren [this message]
2016-05-25 15:42         ` Stephen Warren
     [not found]         ` <5745C7E4.2050908-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-05-26  9:29           ` Joseph Lo
2016-05-26  9:29             ` Joseph Lo
     [not found]             ` <5746C1F1.6070703-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-26 16:29               ` Stephen Warren
2016-05-26 16:29                 ` Stephen Warren

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=5745C7E4.2050908@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
    --cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
    --cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.org \
    /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.