From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
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: Re: [PATCH V2 1/2] dt-bindings: arm: cpus: Extend Qualcomm Oryon compatibles
Date: Sat, 14 Mar 2026 10:58:57 +0100 [thread overview]
Message-ID: <20260314-vegan-clay-roadrunner-8c1af7@quoll> (raw)
In-Reply-To: <20260313103439.1255247-2-sibi.sankar@oss.qualcomm.com>
On Fri, Mar 13, 2026 at 04:04:38PM +0530, Sibi Sankar wrote:
> 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, by appending the
> compatible with MIDR part and variant numbers as listed below.
>
> qcom,oryon-MIDR_EL1[PART_NUM]-MIDR_EL1[VARIANT]
>
> Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/arm/cpus.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-14 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 10:34 [PATCH V2 0/2] " Sibi Sankar
2026-03-13 10:34 ` [PATCH V2 1/2] " Sibi Sankar
2026-03-14 9:58 ` Krzysztof Kozlowski [this message]
2026-03-13 10:34 ` [PATCH V2 2/2] arm64: dts: qcom: glymur: Fix deprecated cpu compatibles Sibi Sankar
2026-03-14 9:59 ` Krzysztof Kozlowski
2026-03-24 16:30 ` Abel Vesa
2026-03-18 13:50 ` [PATCH V2 0/2] dt-bindings: arm: cpus: Extend Qualcomm Oryon compatibles 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=20260314-vegan-clay-roadrunner-8c1af7@quoll \
--to=krzk@kernel.org \
--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=sibi.sankar@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®