public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: Chukun Pan <amadeus@jmu.edu.cn>,
	jonas@kwiboo.se, conor+dt@kernel.org, devicetree@vger.kernel.org,
	heiko@sntech.de, krzk+dt@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh@kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add Radxa ROCK3 Model C
Date: Thu, 18 Apr 2024 07:55:44 +0200	[thread overview]
Message-ID: <9e915ef29a2b49ce56446ec9d474eb64@manjaro.org> (raw)
In-Reply-To: <B26C732A4DCEA9B3+282b8775-601b-4d4a-a513-4924b7940076@radxa.com>

Hello Naoki,

On 2024-04-18 07:52, FUKAUMI Naoki wrote:
> this is Naoki @ Radxa.
> 
> thank you for your great work!
> 
> On 4/18/24 02:02, Dragan Simic wrote:
>> Hello Chukun,
>> 
>> On 2024-04-17 15:30, Chukun Pan wrote:
>>> Hi Jonas,
>>>>> +    model = "Radxa ROCK3 Model C";
>>>> 
>>>> The marketing name seems to be "Radxa ROCK 3C" according to the 
>>>> product
>>>> page at [1].
>>>> 
>>>> [1] https://radxa.com/products/rock3/3c
>>> 
>>> According to https://wiki.radxa.com/Rock3/3c , it should be called
>>> "Radxa ROCK 3 Model C". I copied rock3a here without paying 
>>> attention.
> 
> sorry, wiki.radxa.com is outdated.
> 
> docs.radxa.com is correct one and maintained.
> (but it still has some errors, sorry)
> 
>> If I may interject, here's the result of a quick qrep:
>> 
>> ./rk3399pro-rock-pi-n10.dts:    model = "Radxa ROCK Pi N10";
>> ./rk3399-rock-pi-4a-plus.dts:    model = "Radxa ROCK Pi 4A+";
>> ./rk3588s-rock-5a.dts:    model = "Radxa ROCK 5 Model A";
>> ./rk3588-rock-5b.dts:    model = "Radxa ROCK 5 Model B";
>> ./rk3399-rock-4c-plus.dts:    model = "Radxa ROCK 4C+";
>> ./rk3399-rock-pi-4b-plus.dts:    model = "Radxa ROCK Pi 4B+";
>> ./rk3399-rock-pi-4b.dts:    model = "Radxa ROCK Pi 4B";
>> ./rk3399-rock-pi-4c.dts:    model = "Radxa ROCK Pi 4C";
>> ./rk3308-rock-pi-s.dts:    model = "Radxa ROCK Pi S";
>> ./rk3399-rock-pi-4a.dts:    model = "Radxa ROCK Pi 4A";
>> ./rk3399-rock-4se.dts:    model = "Radxa ROCK 4SE";
>> ./rk3328-rock-pi-e.dts:    model = "Radxa ROCK Pi E";
>> ./rk3568-rock-3a.dts:    model = "Radxa ROCK3 Model A";
>> 
>> Based on that, I think that "Radxa ROCK 3 Model C" would actually
>> be the preferred name...  Perhaps?
>> 
>> If we end up following that approach, the last board dts on the list
>> above should also be fixed to read "Radxa ROCK 3 Model A".
>> 
>> Either that, or all "Model " strings should be stripped out from
>> all board dts files that currently contain it.
> 
> we have a document named "Radxa Product Naming Convention".
> there are "full name" and "short name". "Model" is used in "full
> name", but it's not used in "short name". both are correct.
> 
> but, we preferred to use "short name" for "model = " in mainline 
> linux/u-boot.
> 
> for ROCK 3C, please use
> 
>  model = "Radxa ROCK 3C";
> 
> for ROCK 5A/5B and ROCK 3A,
> 
>  model = "Radxa ROCK 5A";
>  model = "Radxa ROCK 5B";
>  model = "Radxa ROCK 3A";
> 
> are preferred.
> 
> we need to fix this inconsistency. (include our docs)

Great, thanks for this detailed clarification!

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

  reply	other threads:[~2024-04-18  5:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 13:00 [PATCH 1/2] dt-bindings: arm: rockchip: add Radxa ROCK3 Model C Chukun Pan
2024-04-16 13:00 ` [PATCH 2/2] arm64: dts: rockchip: Add " Chukun Pan
2024-04-16 22:10   ` Jonas Karlman
2024-04-17 13:30     ` Chukun Pan
2024-04-17 17:02       ` Dragan Simic
2024-04-18  5:52         ` FUKAUMI Naoki
2024-04-18  5:55           ` Dragan Simic [this message]
2024-04-18  6:33             ` Dragan Simic
2024-04-18  7:18               ` Dragan Simic
2024-04-18  8:31                 ` FUKAUMI Naoki
2024-04-18  8:36                   ` Dragan Simic
2024-05-02 12:45       ` Jonas Karlman
2024-04-17 15:45 ` [PATCH 1/2] dt-bindings: arm: rockchip: add " Krzysztof Kozlowski
2024-04-18  6:13 ` FUKAUMI Naoki

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=9e915ef29a2b49ce56446ec9d474eb64@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.com \
    --cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox