From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Mars Chen <chenxiangrui@huaqin.corp-partner.google.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] CHROMIUM: arm64: dts: qcom: Add sc7180-gelarshie
Date: Thu, 14 Apr 2022 09:10:32 +0200 [thread overview]
Message-ID: <b7ff08b8-60fb-7629-9399-3d5cca46ab9e@linaro.org> (raw)
In-Reply-To: <CAD=FV=UjyLofXZqnj=bL89fza5JS6O5Np9W-A4V4WK+na0hdrw@mail.gmail.com>
On 13/04/2022 23:48, Doug Anderson wrote:
> I'm actually kinda curious: is there really a good reason for this? I
> know I haven't been adding things to
> `Documentation/devicetree/bindings/arm/qcom.yaml` for Qualcomm
> Chromebooks. Ironically, it turns out that the script I typically use
> to invoke checkpatch happens to have "--no-tree" as an argument and
> that seems to disable this check. Doh!
>
> That being said, though, I do wonder a little bit about the value of
> enumerating the top-level compatible like this in a yaml file.
> Certainly the yaml schema validation in general can be quite useful,
> but this top-level listing seems pure overhead. I guess it makes some
> tools happy, but other than that it seems to provide very little
> value...
If compatible is not part of ABI, it is allowed to change in whatever
shape one wishes. In such case, how can anyone (e.g. user-space)
identify the board? Model name? Also not part of ABI (not documented)...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-14 7:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 9:09 [PATCH] CHROMIUM: arm64: dts: qcom: Add sc7180-gelarshie Mars Chen
2022-03-30 14:21 ` kernel test robot
2022-03-30 17:16 ` Matthias Kaehlcke
2022-03-30 17:23 ` Krzysztof Kozlowski
2022-03-30 22:57 ` Rob Clark
2022-03-30 17:25 ` Krzysztof Kozlowski
2022-04-13 21:48 ` Doug Anderson
2022-04-14 7:10 ` Krzysztof Kozlowski [this message]
2022-04-14 17:36 ` Doug Anderson
2022-04-19 15:47 ` Krzysztof Kozlowski
2022-04-19 16:55 ` Doug Anderson
2022-05-03 15:53 ` Krzysztof Kozłowski
2022-05-03 16:13 ` Doug Anderson
2022-05-04 7:04 ` Krzysztof Kozlowski
2022-05-04 23:56 ` Julius Werner
2022-05-06 21:33 ` Doug Anderson
2022-05-07 17:04 ` Krzysztof Kozlowski
2022-05-07 17:11 ` Krzysztof Kozlowski
2022-05-11 2:39 ` Julius Werner
2022-05-11 7:20 ` Krzysztof Kozlowski
2022-05-11 16:09 ` Doug Anderson
2022-05-11 16:57 ` Bjorn Andersson
2022-05-11 17:36 ` Krzysztof Kozlowski
2022-05-11 17:49 ` Doug Anderson
2022-05-12 16:08 ` Doug Anderson
2022-03-30 19:17 ` kernel test robot
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=b7ff08b8-60fb-7629-9399-3d5cca46ab9e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=chenxiangrui@huaqin.corp-partner.google.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).