From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: cpus: Deprecate Qualcomm generic compatibles
Date: Thu, 15 Jan 2026 11:19:47 +0100 [thread overview]
Message-ID: <59ae6b16-7866-413a-a1d2-4a735024c108@oss.qualcomm.com> (raw)
In-Reply-To: <20260115083503.43796-2-krzysztof.kozlowski@oss.qualcomm.com>
On 1/15/26 9:35 AM, Krzysztof Kozlowski wrote:
> Move four compatibles for Qualcomm Krait, Kryo, Oryon and Scorpion
> custom CPU cores out of the enum into separate one with deprecated: true
> annotation, because these are too generic names.
>
> These are names of the families and there are significant differences
> within individual processors, e.g. Kryo6xx can based on architectures
> from Cortex-X2, A710, A510 to A78 and probably more.
>
> Just like other vendor processors are differentiated, also Qualcomm CPUs
> should come with specific compatibles.
>
> Cc: Bjorn Andersson <andersson@kernel.org>
> Cc: Konrad Dybcio <konradybcio@kernel.org>
> Cc: linux-arm-msm@vger.kernel.org
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
[...]
> - - arm,armv8 # Only for s/w models
I'm still bitter about this one existing
$ rg '"arm,armv8"' arch -l | sort
arch/arm64/boot/dts/arm/foundation-v8.dtsi
This makes some sense (see [1])
arch/arm64/boot/dts/arm/fvp-base-revc.dts
arch/arm64/boot/dts/arm/rtsm_ve-aemv8a.dts
These seem to be spawned with a specific virtualized Cortex type
arch/arm64/boot/dts/nvidia/tegra264.dtsi
:(
[1] https://developer.arm.com/documentation/100961/1130/Foundation-Platform-introduction/Platform-overview/Processor-models-in-the-Foundation-Platform?lang=en
Konrad
next prev parent reply other threads:[~2026-01-15 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 8:35 Krzysztof Kozlowski
2026-01-15 9:36 ` Dmitry Baryshkov
2026-01-15 9:45 ` Krzysztof Kozlowski
2026-01-15 10:19 ` Konrad Dybcio [this message]
2026-01-15 18:39 ` Krzysztof Kozlowski
2026-01-15 20:13 ` Rob Herring
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=59ae6b16-7866-413a-a1d2-4a735024c108@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®