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

On Tue, Mar 10, 2026 at 09:37:49AM +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, based on MIDR part and
> variant numbers.

What do the "-x-y" stand for? What are their meanings? Your commit msg
or comment in the file should explain that briefly.

> 
> 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

Best regards,
Krzysztof

On 3/11/2026 3:33 PM, Krzysztof Kozlowski wrote:
> On Tue, Mar 10, 2026 at 09:37:49AM +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, based on MIDR part and
>> variant numbers.
> What do the "-x-y" stand for? What are their meanings? Your commit msg
> or comment in the file should explain that briefly.

Thanks for taking time to review the series :)

-x-y stand for -MIDR_EL1[PART_NUM]-MIDR_EL1[VARIANT]. Will add it
to the commit message.

>> 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
> Best regards,
> Krzysztof
>