From: "Michael Walle" <mwalle@kernel.org>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.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:25:31 +0100 [thread overview]
Message-ID: <CZ8Y4DFQNLM9.3GIGATDIAXBR5@kernel.org> (raw)
In-Reply-To: <72fffc25-33f0-4394-b7c1-8dbc2d23a4a4@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On Mon Feb 19, 2024 at 10:06 AM CET, Krzysztof Kozlowski wrote:
> On 19/02/2024 09:44, Michael Walle wrote:
> > 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
>
> And then it should be part of earlier entry. Just take a look there in
> the file...
FWIW I did and all the entries with descriptions are by there own
(that's also true for fsl.yaml and sunxi.yaml).
mediatek.yaml seems to have both, either boards without description
like the "radxa,nio-12l" which you are probably referring to. Or
boards which has the same sub compatibles but still have individual
entries, like google,burnet, google,cozmo, google,damu.
Therefore, what is the rule of thumb here? Drop the description?
If so, why it it there in the first place?
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2024-02-19 9:25 UTC|newest]
Thread overview: 12+ 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 ` [PATCH v2 2/2] arm64: dts: " Michael Walle
2024-02-19 10:00 ` AngeloGioacchino Del Regno
2024-02-19 13:09 ` Michael Walle
2024-02-19 13:35 ` AngeloGioacchino Del Regno
2024-02-19 13:59 ` Michael Walle
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:25 ` Michael Walle [this message]
2024-02-19 9:23 ` AngeloGioacchino Del Regno
2024-02-19 9:36 ` Michael Walle
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=CZ8Y4DFQNLM9.3GIGATDIAXBR5@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=krzysztof.kozlowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).