From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Yassine Oudjana <yassine.oudjana@gmail.com>
Subject: [PATCH 1/7] dt-bindings: arm: qcom: separate msm8996pro bindings
Date: Sun, 24 Jul 2022 17:04:15 +0300 [thread overview]
Message-ID: <20220724140421.1933004-2-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20220724140421.1933004-1-dmitry.baryshkov@linaro.org>
Xiaomi Mi 5s Plus (natrium) and Xiaomi Mi Note 2 (scorpio) use
MSM8996Pro rather than plain MSM8996. Describe this in the arm/qcom.yaml
bindings.
Since MSM8996Pro is largely compatible with MSM8996, keep old compatible
too rather than insiting on qcom,msm8996pro only. This allows the code
that doesn't yet know about msm8996pro to continue supporting these
devices.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index fb1d00bcc847..3892aedd9215 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -223,8 +223,13 @@ properties:
- sony,kagura-row
- sony,keyaki-row
- xiaomi,gemini
+ - const: qcom,msm8996
+
+ - items:
+ - enum:
- xiaomi,natrium
- xiaomi,scorpio
+ - const: qcom,msm8996pro
- const: qcom,msm8996
- items:
--
2.35.1
next prev parent reply other threads:[~2022-07-24 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 14:04 [PATCH 0/7] arm64: dts: qcom: msm8996: fixes for CPU and GPU OPP tables Dmitry Baryshkov
2022-07-24 14:04 ` Dmitry Baryshkov [this message]
2022-07-26 11:09 ` [PATCH 1/7] dt-bindings: arm: qcom: separate msm8996pro bindings Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 2/7] arm64: dts: qcom: msm8996: Add MSM8996 Pro support Dmitry Baryshkov
2022-07-26 11:09 ` Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 3/7] arm64: dts: qcom: msm8996-xiaomi-scorpio, natrium: Use MSM8996 Pro Dmitry Baryshkov
2022-07-26 11:10 ` Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 4/7] arm64: dts: qcom: msm8996: fix supported-hw in cpufreq OPP tables Dmitry Baryshkov
2022-07-26 11:10 ` Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 5/7] arm64: dts: qcom: msm8996: add support for speed bin 3 Dmitry Baryshkov
2022-07-26 11:10 ` Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 6/7] arm64: dts: qcom: msm8996: fix GPU OPP table Dmitry Baryshkov
2022-07-26 11:10 ` Krzysztof Kozlowski
2022-07-24 14:04 ` [PATCH 7/7] arm64: dts: qcom: msm8996pro: expand Adreno " Dmitry Baryshkov
2022-07-26 11:11 ` Krzysztof Kozlowski
2022-09-16 14:33 ` [PATCH 0/7] arm64: dts: qcom: msm8996: fixes for CPU and GPU OPP tables Dmitry Baryshkov
2022-10-18 3:05 ` Bjorn Andersson
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=20220724140421.1933004-2-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.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=robh+dt@kernel.org \
--cc=yassine.oudjana@gmail.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).