public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	Andrew Bresticker <abrestic@chromium.org>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	devicetree@vger.kernel.org, linux-mips@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute
Date: Mon, 15 Feb 2016 18:52:20 +0100	[thread overview]
Message-ID: <56C21054.4070702@gmx.de> (raw)
In-Reply-To: <56C1B3A0.4090301@cogentembedded.com>

On 02/15/2016 12:16 PM, Sergei Shtylyov wrote:
> Hello.
> 
> On 2/15/2016 8:26 AM, Heinrich Schuchardt wrote:
> 
>> Downstream packages like Debian flash-kernel rely on
>> /proc/device-tree/model
>> to determine how to install an updated kernel image.
>>
>> Most dts files provide this property.
>> It is suggested by IEEE Std 1275-1994.
>>
>> This patch adds a model attribute for Octeon CPUs.
>>
>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
>> ---
>>   arch/mips/boot/dts/cavium-octeon/octeon_3xxx.dts | 1 +
>>   arch/mips/boot/dts/cavium-octeon/octeon_68xx.dts | 1 +
>>   2 files changed, 2 insertions(+)
>>
>> diff --git a/arch/mips/boot/dts/cavium-octeon/octeon_3xxx.dts
>> b/arch/mips/boot/dts/cavium-octeon/octeon_3xxx.dts
>> index 9c48e05..a746678 100644
>> --- a/arch/mips/boot/dts/cavium-octeon/octeon_3xxx.dts
>> +++ b/arch/mips/boot/dts/cavium-octeon/octeon_3xxx.dts
>> @@ -8,6 +8,7 @@
>>    */
>>   / {
>>       compatible = "cavium,octeon-3860";
>> +    model = "Cavium Octeon 3XXX";
>>       #address-cells = <2>;
>>       #size-cells = <2>;
>>       interrupt-parent = <&ciu>;
>> diff --git a/arch/mips/boot/dts/cavium-octeon/octeon_68xx.dts
>> b/arch/mips/boot/dts/cavium-octeon/octeon_68xx.dts
>> index 79b46fc..c8a292a 100644
>> --- a/arch/mips/boot/dts/cavium-octeon/octeon_68xx.dts
>> +++ b/arch/mips/boot/dts/cavium-octeon/octeon_68xx.dts
>> @@ -8,6 +8,7 @@
>>    */
>>   / {
>>       compatible = "cavium,octeon-6880";
>> +    model = "Cavium Octeon 68XX";
>>       #address-cells = <2>;
>>       #size-cells = <2>;
>>       interrupt-parent = <&ciu2>;
> 
>     The ePAPR 1.1 standard says:
> 
> 2.3.2 model
> 
> Property: model
> Value type: <string>
> Description:
>     The model property value is a <string> that specifies the
>      manufacturer’s model number of the device.
> 
>     The recommended format is: “manufacturer,model”, where manufacturer
>     is a string describing the name of the manufacturer (such as a stock
>     ticker symbol), and model specifies the model number.
> 
> Example:
>     model = “fsl,MPC8349EMITX”;
> 
> MBR, Sergei
> 
> 

Hello Sergei, hello Arnd,

thank you for reviewing.

IEEE Std 1275-1994 says stock symbols should be in upper case.

I guess international standards should have precedence over papers valid
for a single architecture (power.org).

Would you support a patch having the following strings?

model = "CAVM, Octeon 3860";
model = "CAVM, Octeon 6880";

Otherwise, please, make a suggestion.

Best regards

Heinrich Schuchardt

  parent reply	other threads:[~2016-02-15 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15  5:26 [PATCH 1/1] MIPS: DTS: cavium-octeon: provide model attribute Heinrich Schuchardt
2016-02-15 11:16 ` Sergei Shtylyov
2016-02-15 11:19   ` Arnd Bergmann
2016-02-15 17:52   ` Heinrich Schuchardt [this message]
2016-02-15 18:11     ` Sergei Shtylyov
2016-02-15 18:35       ` [PATCH 1/1 v2] " Heinrich Schuchardt
2016-02-17  0:20         ` David Daney
2016-02-15 18:38     ` [PATCH 1/1] " Aaro Koskinen
2016-02-15 19:21       ` Heinrich Schuchardt
2016-02-15 19:40         ` Aaro Koskinen
2016-02-15 19:50           ` Heinrich Schuchardt
2016-02-15 19:59             ` Aaro Koskinen

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=56C21054.4070702@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=aaro.koskinen@iki.fi \
    --cc=abrestic@chromium.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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