From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Stephen Boyd <sboyd@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Amit Pundir <amit.pundir@linaro.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
Stephan Gerhold <stephan@gerhold.net>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH 0/4] dt-bindings: arm: qcom: qcom,board-id and qcom,msm-id
Date: Sun, 29 May 2022 22:26:25 +0200 [thread overview]
Message-ID: <20220529202629.47588-1-krzysztof.kozlowski@linaro.org> (raw)
Hi,
The discussion [1] brought several arguments for keeping the qcom,board-id and
qcom,msm-id properties. Keeping means we should document them, so the DT
schema checks pass.
I revived old patch [2] with several changes and improvements. The commit msg
hopefully collects feedback from the discussion.
Best regards,
Krzysztof
[1] https://lore.kernel.org/r/a3c932d1-a102-ce18-deea-18cbbd05ecab@linaro.org/
[2] https://lore.kernel.org/all/1425503602-24916-1-git-send-email-galak@codeaurora.org/
Krzysztof Kozlowski (4):
dt-bindings: arm: qcom: document qcom,msm-id and qcom,board-id
arm64: dts: qcom: msm8992-xiaomi-libra: split qcom,msm-id into tuples
arm64: dts: qcom: msm8998-oneplus: split qcom,board-id into tuples
arm64: dts: qcom: sdm845-oneplus: split qcom,board-id into tuples
.../devicetree/bindings/arm/qcom.yaml | 58 +++++++++++++++++++
.../boot/dts/qcom/msm8992-xiaomi-libra.dts | 2 +-
.../dts/qcom/msm8998-oneplus-cheeseburger.dts | 2 +-
.../dts/qcom/msm8998-oneplus-dumpling.dts | 2 +-
.../dts/qcom/sdm845-oneplus-enchilada.dts | 2 +-
.../boot/dts/qcom/sdm845-oneplus-fajita.dts | 2 +-
include/dt-bindings/arm/qcom,ids.h | 30 ++++++++++
7 files changed, 93 insertions(+), 5 deletions(-)
create mode 100644 include/dt-bindings/arm/qcom,ids.h
--
2.34.1
next reply other threads:[~2022-05-29 20:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 20:26 Krzysztof Kozlowski [this message]
2022-05-29 20:26 ` [PATCH 1/4] dt-bindings: arm: qcom: document qcom,msm-id and qcom,board-id Krzysztof Kozlowski
2022-06-05 15:07 ` Rob Herring
2022-06-07 11:15 ` Krzysztof Kozlowski
2022-06-10 16:33 ` Rob Herring
2022-06-11 13:07 ` Krzysztof Kozlowski
2022-06-13 15:30 ` Rob Herring
2022-06-22 8:29 ` Dmitry Baryshkov
2022-05-29 20:26 ` [PATCH 2/4] arm64: dts: qcom: msm8992-xiaomi-libra: split qcom,msm-id into tuples Krzysztof Kozlowski
2022-05-29 20:26 ` [PATCH 3/4] arm64: dts: qcom: msm8998-oneplus: split qcom,board-id " Krzysztof Kozlowski
2022-05-29 20:26 ` [PATCH 4/4] arm64: dts: qcom: sdm845-oneplus: " Krzysztof Kozlowski
2022-06-03 19:02 ` Stephan Gerhold
2022-06-05 15:42 ` Krzysztof Kozlowski
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=20220529202629.47588-1-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tsoni@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
/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).