From: "Michael Walle" <mwalle@kernel.org>
To: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: <devicetree@vger.kernel.org>,
"Sean Wang" <sean.wang@mediatek.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm64: mediatek: add Kontron 3.5"-SBC-i1200
Date: Mon, 19 Feb 2024 10:36:26 +0100 [thread overview]
Message-ID: <CZ8YCQETS7LL.1BLJJZNCLV7DT@kernel.org> (raw)
In-Reply-To: <ed3530f0-227a-47f2-938c-28eba90dd6eb@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
On Mon Feb 19, 2024 at 10:23 AM CET, AngeloGioacchino Del Regno wrote:
> Il 19/02/24 09:44, Michael Walle ha scritto:
> > Add the compatible string for the Kontron 3.5"-SBC-i1200 single board
> > computer.
> >
> > Signed-off-by: Michael Walle <mwalle@kernel.org>
> > ---
> > v2:
> > - convert enum to const as there is only one specific board
> >
> > Documentation/devicetree/bindings/arm/mediatek.yaml | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> > index 09f9ffd3ff7b..add167d8b8da 100644
> > --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> > +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> > @@ -357,6 +357,11 @@ properties:
> > - radxa,nio-12l
> > - const: mediatek,mt8395
> > - const: mediatek,mt8195
> > + - description: Kontron 3.5"-SBC-i1200
> > + items:
> > + - const: kontron,3-5-sbc-i1200
> > + - const: mediatek,mt8395
> > + - const: mediatek,mt8195
> > - items:
> > - enum:
> > - mediatek,mt8516-pumpkin
>
> I understand that you took inspiration from the Google Chromebooks entries, but
> those are separated only because they've got "a bunch of revisions".
>
I don't really care about the description. It's just the way I've
done it in the past. And in this file, there is also google,burnet,
google,cozmo, google,damu, without any further revs.
> For machines that don't have a billion compatible strings, I would suggest to
> add the compatible under a single big entry: like this, the binding is (imo) a
> bit more readable .. and cleaner.
>
> Eventually, the machine name is in the devicetree so we're not losing any kind
> of information anyway... :-)
>
> - items:
> - enum:
> - kontron,3-5-sbc-i1200
> - mediatek,mt8395-evk
> - radxa,nio-12l
> - const: mediatek,mt8395
> - const: mediatek,mt8195
Ack. I'll give you some time to look at the actual DTS before
posting a new version.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Walle" <mwalle@kernel.org>
To: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: <devicetree@vger.kernel.org>,
"Sean Wang" <sean.wang@mediatek.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: arm64: mediatek: add Kontron 3.5"-SBC-i1200
Date: Mon, 19 Feb 2024 10:36:26 +0100 [thread overview]
Message-ID: <CZ8YCQETS7LL.1BLJJZNCLV7DT@kernel.org> (raw)
In-Reply-To: <ed3530f0-227a-47f2-938c-28eba90dd6eb@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 2234 bytes --]
On Mon Feb 19, 2024 at 10:23 AM CET, AngeloGioacchino Del Regno wrote:
> Il 19/02/24 09:44, Michael Walle ha scritto:
> > Add the compatible string for the Kontron 3.5"-SBC-i1200 single board
> > computer.
> >
> > Signed-off-by: Michael Walle <mwalle@kernel.org>
> > ---
> > v2:
> > - convert enum to const as there is only one specific board
> >
> > Documentation/devicetree/bindings/arm/mediatek.yaml | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/mediatek.yaml b/Documentation/devicetree/bindings/arm/mediatek.yaml
> > index 09f9ffd3ff7b..add167d8b8da 100644
> > --- a/Documentation/devicetree/bindings/arm/mediatek.yaml
> > +++ b/Documentation/devicetree/bindings/arm/mediatek.yaml
> > @@ -357,6 +357,11 @@ properties:
> > - radxa,nio-12l
> > - const: mediatek,mt8395
> > - const: mediatek,mt8195
> > + - description: Kontron 3.5"-SBC-i1200
> > + items:
> > + - const: kontron,3-5-sbc-i1200
> > + - const: mediatek,mt8395
> > + - const: mediatek,mt8195
> > - items:
> > - enum:
> > - mediatek,mt8516-pumpkin
>
> I understand that you took inspiration from the Google Chromebooks entries, but
> those are separated only because they've got "a bunch of revisions".
>
I don't really care about the description. It's just the way I've
done it in the past. And in this file, there is also google,burnet,
google,cozmo, google,damu, without any further revs.
> For machines that don't have a billion compatible strings, I would suggest to
> add the compatible under a single big entry: like this, the binding is (imo) a
> bit more readable .. and cleaner.
>
> Eventually, the machine name is in the devicetree so we're not losing any kind
> of information anyway... :-)
>
> - items:
> - enum:
> - kontron,3-5-sbc-i1200
> - mediatek,mt8395-evk
> - radxa,nio-12l
> - const: mediatek,mt8395
> - const: mediatek,mt8195
Ack. I'll give you some time to look at the actual DTS before
posting a new version.
-michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-19 9:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 8:44 [PATCH v2 1/2] dt-bindings: arm64: mediatek: add Kontron 3.5"-SBC-i1200 Michael Walle
2024-02-19 8:44 ` Michael Walle
2024-02-19 8:44 ` [PATCH v2 2/2] arm64: dts: " Michael Walle
2024-02-19 8:44 ` Michael Walle
2024-02-19 10:00 ` AngeloGioacchino Del Regno
2024-02-19 10:00 ` AngeloGioacchino Del Regno
2024-02-19 13:09 ` Michael Walle
2024-02-19 13:09 ` Michael Walle
2024-02-19 13:35 ` AngeloGioacchino Del Regno
2024-02-19 13:35 ` AngeloGioacchino Del Regno
2024-02-19 13:59 ` Michael Walle
2024-02-19 13:59 ` Michael Walle
2024-02-20 8:54 ` AngeloGioacchino Del Regno
2024-02-20 8:54 ` AngeloGioacchino Del Regno
2024-02-19 9:06 ` [PATCH v2 1/2] dt-bindings: arm64: " Krzysztof Kozlowski
2024-02-19 9:06 ` Krzysztof Kozlowski
2024-02-19 9:25 ` Michael Walle
2024-02-19 9:25 ` Michael Walle
2024-02-19 9:23 ` AngeloGioacchino Del Regno
2024-02-19 9:23 ` AngeloGioacchino Del Regno
2024-02-19 9:36 ` Michael Walle [this message]
2024-02-19 9:36 ` Michael Walle
2024-02-19 10:07 ` AngeloGioacchino Del Regno
2024-02-19 10:07 ` 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=CZ8YCQETS7LL.1BLJJZNCLV7DT@kernel.org \
--to=mwalle@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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=sean.wang@mediatek.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 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.