[PATCH v1 0/2] Add initial Maili SoC support

[PATCH v1 0/2] Add initial Maili SoC support

[Prasad Kumpatla]

This series introduces the Maili SoC compatible string in the DT
bindings and adds the corresponding pd-mapper support required for the
platform.

Prasad Kumpatla (1):
  soc: qcom: pd-mapper: Add support for Maili SoC

Yijie Yang (1):
  dt-bindings: arm: qcom: Add Maili SoC compatible

 Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
 drivers/soc/qcom/qcom_pd_mapper.c               | 1 +
 2 files changed, 4 insertions(+)

-- 
2.34.1

[PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Prasad Kumpatla]

From: Yijie Yang <yijie.yang@oss.qualcomm.com>

Add the qcom,maili SoC compatible string to the QCOM SoC bindings.

Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index ff8a35df7862..00d9a493fe76 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -175,6 +175,9 @@ properties:
               - qcom,kaanapali-qrd
           - const: qcom,kaanapali
 
+      - items:
+          - const: qcom,maili
+
       - items:
           - enum:
               - qcom,mahua-crd
-- 
2.34.1

[PATCH v1 2/2] soc: qcom: pd-mapper: Add support for Maili SoC

[Prasad Kumpatla]

Add support for the Qualcomm Maili SoC to the protection
domain mapper. Maili shares the same protection domain
configuration as Kaanapali, so reuse the existing
Kaanapali domain data.

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
---
 drivers/soc/qcom/qcom_pd_mapper.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
index 64ca99d7fad9..3376423d237f 100644
--- a/drivers/soc/qcom/qcom_pd_mapper.c
+++ b/drivers/soc/qcom/qcom_pd_mapper.c
@@ -626,6 +626,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
 	{ .compatible = "qcom,hawi", .data = kaanapali_domains, },
 	{ .compatible = "qcom,kaanapali", .data = kaanapali_domains, },
 	{ .compatible = "qcom,mahua", .data = glymur_domains, },
+	{ .compatible = "qcom,maili", .data = kaanapali_domains, },
 	{ .compatible = "qcom,milos", .data = sm8550_domains, },
 	{ .compatible = "qcom,msm8226", .data = NULL, },
 	{ .compatible = "qcom,msm8909", .data = NULL, },
-- 
2.34.1

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Jingyi Wang]

On 8/19/2026 1:42 PM, Prasad Kumpatla wrote:
> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> 
> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---

your SOB is missing

Thanks,
Jingyi

>   Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862..00d9a493fe76 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -175,6 +175,9 @@ properties:
>                 - qcom,kaanapali-qrd
>             - const: qcom,kaanapali
>   
> +      - items:
> +          - const: qcom,maili
> +
>         - items:
>             - enum:
>                 - qcom,mahua-crd

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The new compatible string block for `qcom,maili` breaks the alphabetical sorting order of the SoC list.
--

--- Patch [1]: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible ---
commit e26e69cd7b7d4cf716af221adce51d02ada71b52
Author: Yijie Yang <yijie.yang@oss.qualcomm.com>

dt-bindings: arm: qcom: Add Maili SoC compatible

This commit adds the qcom,maili SoC compatible string to the QCOM SoC
device tree bindings.

> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862d..00d9a493fe766 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml

[ ... ]

> @@ -175,6 +175,9 @@ properties:
>                - qcom,kaanapali-qrd
>            - const: qcom,kaanapali
>  
> +      - items:
> +          - const: qcom,maili
> +
>        - items:
>            - enum:
>                - qcom,mahua-crd

[Severity: Low]
This isn't a bug, but does this addition break the alphabetical sorting
of the compatible strings? It looks like qcom,maili is being placed
before qcom,mahua-crd, but 'i' comes after 'h'.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260819054203.61385-1-prasad.kumpatla@oss.qualcomm.com?part=1

Re: [PATCH v1 0/2] Add initial Maili SoC support

[Jingyi Wang]

I think it could be better to have a more specific title like
"Add support for Qualcomm Maili pd-mapper?"

Thanks,
Jingyi

On 8/19/2026 1:42 PM, Prasad Kumpatla wrote:
> This series introduces the Maili SoC compatible string in the DT
> bindings and adds the corresponding pd-mapper support required for the
> platform.
> 
> Prasad Kumpatla (1):
>    soc: qcom: pd-mapper: Add support for Maili SoC
> 
> Yijie Yang (1):
>    dt-bindings: arm: qcom: Add Maili SoC compatible
> 
>   Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>   drivers/soc/qcom/qcom_pd_mapper.c               | 1 +
>   2 files changed, 4 insertions(+)
> 

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Prasad Kumpatla]

On 8/19/2026 11:20 AM, Jingyi Wang wrote:
>
>
> On 8/19/2026 1:42 PM, Prasad Kumpatla wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>
> your SOB is missing

Ack, will update in v2.

Thanks,
Prasad

>
> Thanks,
> Jingyi
>
>> Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml 
>> b/Documentation/devicetree/bindings/arm/qcom.yaml
>> index ff8a35df7862..00d9a493fe76 100644
>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>> @@ -175,6 +175,9 @@ properties:
>>                 - qcom,kaanapali-qrd
>>             - const: qcom,kaanapali
>>   +      - items:
>> +          - const: qcom,maili
>> +
>>         - items:
>>             - enum:
>>                 - qcom,mahua-crd
>

Re: [PATCH v1 0/2] Add initial Maili SoC support

[Prasad Kumpatla]

On 8/19/2026 11:24 AM, Jingyi Wang wrote:
> I think it could be better to have a more specific title like
> "Add support for Qualcomm Maili pd-mapper?"

Sure, will Update.

Thanks,
Prasad

>
> Thanks,
> Jingyi
>
> On 8/19/2026 1:42 PM, Prasad Kumpatla wrote:
>> This series introduces the Maili SoC compatible string in the DT
>> bindings and adds the corresponding pd-mapper support required for the
>> platform.
>>
>> Prasad Kumpatla (1):
>>    soc: qcom: pd-mapper: Add support for Maili SoC
>>
>> Yijie Yang (1):
>>    dt-bindings: arm: qcom: Add Maili SoC compatible
>>
>>   Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>   drivers/soc/qcom/qcom_pd_mapper.c               | 1 +
>>   2 files changed, 4 insertions(+)
>>
>

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Krzysztof Kozlowski]

On 19/08/2026 07:42, Prasad Kumpatla wrote:
> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
> 
> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862..00d9a493fe76 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -175,6 +175,9 @@ properties:
>                - qcom,kaanapali-qrd
>            - const: qcom,kaanapali
>  
> +      - items:
> +          - const: qcom,maili

Heh? This cannot go alone.

Best regards,
Krzysztof

Re: [PATCH v1 2/2] soc: qcom: pd-mapper: Add support for Maili SoC

[Krzysztof Kozlowski]

On 19/08/2026 07:42, Prasad Kumpatla wrote:
> Add support for the Qualcomm Maili SoC to the protection
> domain mapper. Maili shares the same protection domain
> configuration as Kaanapali, so reuse the existing
> Kaanapali domain data.
> 
> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> Signed-off-by: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>
> ---
>  drivers/soc/qcom/qcom_pd_mapper.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/soc/qcom/qcom_pd_mapper.c b/drivers/soc/qcom/qcom_pd_mapper.c
> index 64ca99d7fad9..3376423d237f 100644
> --- a/drivers/soc/qcom/qcom_pd_mapper.c
> +++ b/drivers/soc/qcom/qcom_pd_mapper.c
> @@ -626,6 +626,7 @@ static const struct of_device_id qcom_pdm_domains[] __maybe_unused = {
>  	{ .compatible = "qcom,hawi", .data = kaanapali_domains, },
>  	{ .compatible = "qcom,kaanapali", .data = kaanapali_domains, },
>  	{ .compatible = "qcom,mahua", .data = glymur_domains, },
> +	{ .compatible = "qcom,maili", .data = kaanapali_domains, },

This patchset makes no sense. Early upstreaming of unreleased SoC does
not mean you send everything except DTS. You send things earlier to
speed up merging, but such trivialities targeting Qcom SoC should be
sent with the SoC DTS. It brings no value to send it earlier.

Best regards,
Krzysztof

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Yijie Yang]

On 8/19/2026 2:09 PM, Krzysztof Kozlowski wrote:
> On 19/08/2026 07:42, Prasad Kumpatla wrote:
>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
>> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
>>
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>>   Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>> index ff8a35df7862..00d9a493fe76 100644
>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>> @@ -175,6 +175,9 @@ properties:
>>                 - qcom,kaanapali-qrd
>>             - const: qcom,kaanapali
>>   
>> +      - items:
>> +          - const: qcom,maili
> 
> Heh? This cannot go alone.

Keep only the SoC compatible string and exclude the board for now, as 
the latter is not currently used.
https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Krzysztof Kozlowski]

On 19/08/2026 08:28, Yijie Yang wrote:
> 
> 
> On 8/19/2026 2:09 PM, Krzysztof Kozlowski wrote:
>> On 19/08/2026 07:42, Prasad Kumpatla wrote:
>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>
>>> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
>>>
>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>> ---
>>>   Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> index ff8a35df7862..00d9a493fe76 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> @@ -175,6 +175,9 @@ properties:
>>>                 - qcom,kaanapali-qrd
>>>             - const: qcom,kaanapali
>>>   
>>> +      - items:
>>> +          - const: qcom,maili
>>
>> Heh? This cannot go alone.
> 
> Keep only the SoC compatible string and exclude the board for now, as 
> the latter is not currently used.
> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/

No, read my message there - this should be rejected! I even wrote:

"But if ever this commit is used in argument "oh, compatible without
user was accepted here by Krzysztof, so I can do the same", I will
simply NAK such future contribution without reading the rest."

So NAK because you did not even bother to read what I already stated!

Best regards,
Krzysztof

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Yijie Yang]

On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
> On 19/08/2026 08:28, Yijie Yang wrote:
>>
>>
>> On 8/19/2026 2:09 PM, Krzysztof Kozlowski wrote:
>>> On 19/08/2026 07:42, Prasad Kumpatla wrote:
>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>
>>>> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
>>>>
>>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>> ---
>>>>    Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>>>    1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> index ff8a35df7862..00d9a493fe76 100644
>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>> @@ -175,6 +175,9 @@ properties:
>>>>                  - qcom,kaanapali-qrd
>>>>              - const: qcom,kaanapali
>>>>    
>>>> +      - items:
>>>> +          - const: qcom,maili
>>>
>>> Heh? This cannot go alone.
>>
>> Keep only the SoC compatible string and exclude the board for now, as
>> the latter is not currently used.
>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
> 
> No, read my message there - this should be rejected! I even wrote:
> 
> "But if ever this commit is used in argument "oh, compatible without
> user was accepted here by Krzysztof, so I can do the same", I will
> simply NAK such future contribution without reading the rest."
> 
> So NAK because you did not even bother to read what I already stated!

In patch 2/2, pd-mapper serves as the user. Is there any other reason to 
reject this binding?

> 
> Best regards,
> Krzysztof

-- 
Best Regards,
Yijie

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Krzysztof Kozlowski]

On 19/08/2026 09:02, Yijie Yang wrote:
> 
> 
> On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
>> On 19/08/2026 08:28, Yijie Yang wrote:
>>>
>>>
>>> On 8/19/2026 2:09 PM, Krzysztof Kozlowski wrote:
>>>> On 19/08/2026 07:42, Prasad Kumpatla wrote:
>>>>> From: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>>
>>>>> Add the qcom,maili SoC compatible string to the QCOM SoC bindings.
>>>>>
>>>>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>>>>> ---
>>>>>    Documentation/devicetree/bindings/arm/qcom.yaml | 3 +++
>>>>>    1 file changed, 3 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>> index ff8a35df7862..00d9a493fe76 100644
>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>> @@ -175,6 +175,9 @@ properties:
>>>>>                  - qcom,kaanapali-qrd
>>>>>              - const: qcom,kaanapali
>>>>>    
>>>>> +      - items:
>>>>> +          - const: qcom,maili
>>>>
>>>> Heh? This cannot go alone.
>>>
>>> Keep only the SoC compatible string and exclude the board for now, as
>>> the latter is not currently used.
>>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
>>
>> No, read my message there - this should be rejected! I even wrote:
>>
>> "But if ever this commit is used in argument "oh, compatible without
>> user was accepted here by Krzysztof, so I can do the same", I will
>> simply NAK such future contribution without reading the rest."
>>
>> So NAK because you did not even bother to read what I already stated!
> 
> In patch 2/2, pd-mapper serves as the user. Is there any other reason to 
> reject this binding?

I already wrote - this compatible cannot go alone. It makes no sense
alone. Otherwise explain me what are you expressing here? Because commit
msg did not help me to understand it - it just repeats the diff, which
is pointless.

So why are you doing this?

Best regards,
Krzysztof

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Konrad Dybcio]

On 8/19/26 9:02 AM, Yijie Yang wrote:
> 
> 
> On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
>> On 19/08/2026 08:28, Yijie Yang wrote:

[...]

>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>> @@ -175,6 +175,9 @@ properties:
>>>>>                  - qcom,kaanapali-qrd
>>>>>              - const: qcom,kaanapali
>>>>>    +      - items:
>>>>> +          - const: qcom,maili
>>>>
>>>> Heh? This cannot go alone.
>>>
>>> Keep only the SoC compatible string and exclude the board for now, as
>>> the latter is not currently used.
>>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
>>
>> No, read my message there - this should be rejected! I even wrote:
>>
>> "But if ever this commit is used in argument "oh, compatible without
>> user was accepted here by Krzysztof, so I can do the same", I will
>> simply NAK such future contribution without reading the rest."
>>
>> So NAK because you did not even bother to read what I already stated!
> 
> In patch 2/2, pd-mapper serves as the user. Is there any other reason to reject this binding?

This defines/allows a top-level compatible of

compatible = "qcom,maili";

which is missing the board part, and that is strictly required.

Konrad

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Krzysztof Kozlowski]

On 19/08/2026 10:56, Konrad Dybcio wrote:
> On 8/19/26 9:02 AM, Yijie Yang wrote:
>>
>>
>> On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
>>> On 19/08/2026 08:28, Yijie Yang wrote:
> 
> [...]
> 
>>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>> @@ -175,6 +175,9 @@ properties:
>>>>>>                  - qcom,kaanapali-qrd
>>>>>>              - const: qcom,kaanapali
>>>>>>    +      - items:
>>>>>> +          - const: qcom,maili
>>>>>
>>>>> Heh? This cannot go alone.
>>>>
>>>> Keep only the SoC compatible string and exclude the board for now, as
>>>> the latter is not currently used.
>>>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
>>>
>>> No, read my message there - this should be rejected! I even wrote:
>>>
>>> "But if ever this commit is used in argument "oh, compatible without
>>> user was accepted here by Krzysztof, so I can do the same", I will
>>> simply NAK such future contribution without reading the rest."
>>>
>>> So NAK because you did not even bother to read what I already stated!
>>
>> In patch 2/2, pd-mapper serves as the user. Is there any other reason to reject this binding?
> 
> This defines/allows a top-level compatible of
> 
> compatible = "qcom,maili";
> 
> which is missing the board part, and that is strictly required.

Not sure if you are agreeing with me or disagreeing...

Best regards,
Krzysztof

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Konrad Dybcio]

On 8/19/26 11:04 AM, Krzysztof Kozlowski wrote:
> On 19/08/2026 10:56, Konrad Dybcio wrote:
>> On 8/19/26 9:02 AM, Yijie Yang wrote:
>>>
>>>
>>> On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
>>>> On 19/08/2026 08:28, Yijie Yang wrote:
>>
>> [...]
>>
>>>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>>> @@ -175,6 +175,9 @@ properties:
>>>>>>>                  - qcom,kaanapali-qrd
>>>>>>>              - const: qcom,kaanapali
>>>>>>>    +      - items:
>>>>>>> +          - const: qcom,maili
>>>>>>
>>>>>> Heh? This cannot go alone.
>>>>>
>>>>> Keep only the SoC compatible string and exclude the board for now, as
>>>>> the latter is not currently used.
>>>>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
>>>>
>>>> No, read my message there - this should be rejected! I even wrote:
>>>>
>>>> "But if ever this commit is used in argument "oh, compatible without
>>>> user was accepted here by Krzysztof, so I can do the same", I will
>>>> simply NAK such future contribution without reading the rest."
>>>>
>>>> So NAK because you did not even bother to read what I already stated!
>>>
>>> In patch 2/2, pd-mapper serves as the user. Is there any other reason to reject this binding?
>>
>> This defines/allows a top-level compatible of
>>
>> compatible = "qcom,maili";
>>
>> which is missing the board part, and that is strictly required.
> 
> Not sure if you are agreeing with me or disagreeing...

Agreeing - I'm saying that we need the board compatible to be present
in the tuple, which the submission doesn't contain

Konrad

Re: [PATCH v1 1/2] dt-bindings: arm: qcom: Add Maili SoC compatible

[Yijie Yang]

On 8/19/2026 5:05 PM, Konrad Dybcio wrote:
> On 8/19/26 11:04 AM, Krzysztof Kozlowski wrote:
>> On 19/08/2026 10:56, Konrad Dybcio wrote:
>>> On 8/19/26 9:02 AM, Yijie Yang wrote:
>>>>
>>>>
>>>> On 8/19/2026 2:35 PM, Krzysztof Kozlowski wrote:
>>>>> On 19/08/2026 08:28, Yijie Yang wrote:
>>>
>>> [...]
>>>
>>>>>>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>>>>>>> @@ -175,6 +175,9 @@ properties:
>>>>>>>>                   - qcom,kaanapali-qrd
>>>>>>>>               - const: qcom,kaanapali
>>>>>>>>     +      - items:
>>>>>>>> +          - const: qcom,maili
>>>>>>>
>>>>>>> Heh? This cannot go alone.
>>>>>>
>>>>>> Keep only the SoC compatible string and exclude the board for now, as
>>>>>> the latter is not currently used.
>>>>>> https://lore.kernel.org/all/20260622-brainy-rapid-tody-dd7c3a@quoll/
>>>>>
>>>>> No, read my message there - this should be rejected! I even wrote:
>>>>>
>>>>> "But if ever this commit is used in argument "oh, compatible without
>>>>> user was accepted here by Krzysztof, so I can do the same", I will
>>>>> simply NAK such future contribution without reading the rest."
>>>>>
>>>>> So NAK because you did not even bother to read what I already stated!
>>>>
>>>> In patch 2/2, pd-mapper serves as the user. Is there any other reason to reject this binding?
>>>
>>> This defines/allows a top-level compatible of
>>>
>>> compatible = "qcom,maili";
>>>
>>> which is missing the board part, and that is strictly required.
>>
>> Not sure if you are agreeing with me or disagreeing...
> 
> Agreeing - I'm saying that we need the board compatible to be present
> in the tuple, which the submission doesn't contain
> 
> Konrad

Okay, will hold this binding for now.

-- 
Best Regards,
Yijie