Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	andersson@kernel.org, konradybcio@kernel.org
Cc: sudeep.holla@kernel.org, angelogioacchino.delregno@collabora.com,
	viresh.kumar@linaro.org, neil.armstrong@linaro.org,
	festevam@gmail.com, Frank.Li@nxp.com, danila@jiaxyga.com,
	lpieralisi@kernel.org, dmitry.baryshkov@oss.qualcomm.com,
	tengfei.fan@oss.qualcomm.com, jingyi.wang@oss.qualcomm.com,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] dt-bindings: arm: cpus: Extend Qualcomm Oryon compatibles
Date: Tue, 10 Mar 2026 09:37:49 +0530	[thread overview]
Message-ID: <20260310040751.3132523-2-sibi.sankar@oss.qualcomm.com> (raw)
In-Reply-To: <20260310040751.3132523-1-sibi.sankar@oss.qualcomm.com>

The generic Qualcomm Oryon CPU compatible documented in the binding
doesn't account for differences between core types and has been
deprecated. Introduce core-specific compatibles, based on MIDR part and
variant numbers.

Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/arm/cpus.yaml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
index 700255e9a002..fb6e5871b625 100644
--- a/Documentation/devicetree/bindings/arm/cpus.yaml
+++ b/Documentation/devicetree/bindings/arm/cpus.yaml
@@ -218,6 +218,13 @@ properties:
           - qcom,kryo685
           - qcom,kryo780
           - qcom,scorpion
+          - qcom,oryon-1-1
+          - qcom,oryon-1-2
+          - qcom,oryon-1-3
+          - qcom,oryon-1-4
+          - qcom,oryon-2-1
+          - qcom,oryon-2-2
+          - qcom,oryon-2-3
           - samsung,mongoose-m2
           - samsung,mongoose-m3
           - samsung,mongoose-m5
-- 
2.34.1


  reply	other threads:[~2026-03-10  4:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  4:07 [PATCH 0/3] dt-bindings: arm: cpus: Extend Qualcomm Oryon compatibles Sibi Sankar
2026-03-10  4:07 ` Sibi Sankar [this message]
2026-03-11 10:03   ` [PATCH 1/3] " Krzysztof Kozlowski
2026-03-11 10:21     ` Sibi Sankar
2026-03-10  4:07 ` [PATCH 2/3] arm64: dts: qcom: glymur: Fix deprecated cpu compatibles Sibi Sankar
2026-03-10  4:07 ` [PATCH 3/3] arm64: dts: qcom: kaanapali: " Sibi Sankar
2026-03-11 10:04   ` Krzysztof Kozlowski
2026-03-11 10:21     ` Krzysztof Kozlowski
2026-03-11 10:32       ` Sibi Sankar
2026-03-11 10:36         ` Krzysztof Kozlowski
2026-03-11 10:38           ` Sibi Sankar

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=20260310040751.3132523-2-sibi.sankar@oss.qualcomm.com \
    --to=sibi.sankar@oss.qualcomm.com \
    --cc=Frank.Li@nxp.com \
    --cc=andersson@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=danila@jiaxyga.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=festevam@gmail.com \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=tengfei.fan@oss.qualcomm.com \
    --cc=viresh.kumar@linaro.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