From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Hsin-Te Yuan <yuanhsinte@chromium.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 2/2] dt-bindings: arm64: mediatek: Add kukui-jacuzzi-cerise board
Date: Wed, 31 Jul 2024 10:47:54 +0200 [thread overview]
Message-ID: <909d4058-e3e9-4b59-b476-8f78e668c73b@collabora.com> (raw)
In-Reply-To: <bb696e60-642f-43f1-9ccf-972e1d839bcd@kernel.org>
Il 31/07/24 10:16, Krzysztof Kozlowski ha scritto:
> On 31/07/2024 08:26, Hsin-Te Yuan wrote:
>> Cerise is known as ASUS Chromebook CZ1.
>> Stern is known as ASUS Chromebook Flip CZ1.
>>
>> They are almost identical. The only difference is that Cerise is a
>> clamshell device without touchscreen and Stern is a convertible device.
>>
>> Signed-off-by: Hsin-Te Yuan <yuanhsinte@chromium.org>
>> ---
>> Documentation/devicetree/bindings/arm/mediatek.yaml | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
>> index 1d4bb50fcd8d..087773a43673 100644
>> --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
>> +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
>> @@ -146,6 +146,20 @@ properties:
>> items:
>> - const: google,burnet
>> - const: mediatek,mt8183
>> + - description: Google Cerise (ASUS Chromebook CZ1)
>> + items:
>> + - enum:
>> + - google,cerise-sku0
>> + - google,cerise-rev3-sku0
>> + - const: google,cerise
>> + - const: mediatek,mt8183
>> + - description: Google Stern (ASUS Chromebook Flip CZ1)
>> + items:
>> + - enum:
>> + - google,cerise-sku1
>> + - google,cerise-rev3-sku1
>> + - const: google,cerise
>
> Why not google,stern? If this is not compatible with cerise and has
> different name, I think logical would be to have different compatible -
> either here or the first one.
>
They're both compatible, but the commercial names are different because one
is convertible, one is not... and the bootloader still checks for cerise
even on stern - that's how I read it, and it's not the first time...
...but it doesn't hurt to have a "google,stern" compatible added to the mix,
it's just one more const to add... and I don't have any strong opinion about
that, so, Hsin-Te, it's your call. :-)
Cheers,
Angelo
next prev parent reply other threads:[~2024-07-31 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 6:26 [PATCH v2 0/2] Add kukui-jacuzzi-cerise and kukui-jacuzzi-stern DT and dt-binding Hsin-Te Yuan
2024-07-31 6:26 ` [PATCH v2 1/2] arm64: dts: mt8183: Add kukui-jacuzzi-cerise series boards Hsin-Te Yuan
2024-07-31 8:21 ` AngeloGioacchino Del Regno
2024-07-31 6:26 ` [PATCH v2 2/2] dt-bindings: arm64: mediatek: Add kukui-jacuzzi-cerise board Hsin-Te Yuan
2024-07-31 8:16 ` Krzysztof Kozlowski
2024-07-31 8:47 ` AngeloGioacchino Del Regno [this message]
2024-07-31 9:44 ` Krzysztof Kozlowski
2024-07-31 8:19 ` AngeloGioacchino Del Regno
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=909d4058-e3e9-4b59-b476-8f78e668c73b@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=yuanhsinte@chromium.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