[PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Yijie Yang]

Document compatible string for the FastRPC interface on the Qualcomm Maili
SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
fallback to Kaanapali.

Assisted-by: Claude:claude-opus-4-6
Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
---
 Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
index 2876fdd7c6e6..afe52296bf1d 100644
--- a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
+++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
@@ -26,6 +26,7 @@ properties:
           - enum:
               - qcom,glymur-fastrpc
               - qcom,hawi-fastrpc
+              - qcom,maili-fastrpc
           - const: qcom,kaanapali-fastrpc
 
   label:

---
base-commit: 550604d6c9b9efc8d068aff94dc301694a7afdee
change-id: 20260512-fastrpc-9f3b691f8e2d

Best regards,
--  
Yijie Yang <yijie.yang@oss.qualcomm.com>

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Dmitry Baryshkov]

On Mon, May 25, 2026 at 02:21:17PM +0800, Yijie Yang wrote:
> Document compatible string for the FastRPC interface on the Qualcomm Maili
> SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
> fallback to Kaanapali.

Can I assume that it has the same bus width as Kaanapali?

> 
> Assisted-by: Claude:claude-opus-4-6

Claude assisting to write a one-liner patch? It's becoming ridiculous.

> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
> index 2876fdd7c6e6..afe52296bf1d 100644
> --- a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
> +++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
> @@ -26,6 +26,7 @@ properties:
>            - enum:
>                - qcom,glymur-fastrpc
>                - qcom,hawi-fastrpc
> +              - qcom,maili-fastrpc
>            - const: qcom,kaanapali-fastrpc
>  
>    label:
> 
> ---
> base-commit: 550604d6c9b9efc8d068aff94dc301694a7afdee
> change-id: 20260512-fastrpc-9f3b691f8e2d
> 
> Best regards,
> --  
> Yijie Yang <yijie.yang@oss.qualcomm.com>
> 

-- 
With best wishes
Dmitry

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Yijie Yang]

On 5/25/2026 4:37 PM, Dmitry Baryshkov wrote:
> On Mon, May 25, 2026 at 02:21:17PM +0800, Yijie Yang wrote:
>> Document compatible string for the FastRPC interface on the Qualcomm Maili
>> SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
>> fallback to Kaanapali.
> 
> Can I assume that it has the same bus width as Kaanapali?

Yes, the DMA width for CDSP and ADSP is the same. If you were referring 
to something other than the DMA width, please let me know.

> 
>>
>> Assisted-by: Claude:claude-opus-4-6
> 
> Claude assisting to write a one-liner patch? It's becoming ridiculous.

This patch was generated alongside a set of Maili-related patches and 
was not created specifically on its own.

> 
>> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
>> ---
>>   Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
>> index 2876fdd7c6e6..afe52296bf1d 100644
>> --- a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
>> +++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml
>> @@ -26,6 +26,7 @@ properties:
>>             - enum:
>>                 - qcom,glymur-fastrpc
>>                 - qcom,hawi-fastrpc
>> +              - qcom,maili-fastrpc
>>             - const: qcom,kaanapali-fastrpc
>>   
>>     label:
>>
>> ---
>> base-commit: 550604d6c9b9efc8d068aff94dc301694a7afdee
>> change-id: 20260512-fastrpc-9f3b691f8e2d
>>
>> Best regards,
>> --
>> Yijie Yang <yijie.yang@oss.qualcomm.com>
>>
> 

-- 
Best Regards,
Yijie

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Dmitry Baryshkov]

On Mon, May 25, 2026 at 05:37:23PM +0800, Yijie Yang wrote:
> 
> 
> On 5/25/2026 4:37 PM, Dmitry Baryshkov wrote:
> > On Mon, May 25, 2026 at 02:21:17PM +0800, Yijie Yang wrote:
> > > Document compatible string for the FastRPC interface on the Qualcomm Maili
> > > SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
> > > fallback to Kaanapali.
> > 
> > Can I assume that it has the same bus width as Kaanapali?
> 
> Yes, the DMA width for CDSP and ADSP is the same. If you were referring to
> something other than the DMA width, please let me know.

Thanks for the confirmation.

> 
> > 
> > > 
> > > Assisted-by: Claude:claude-opus-4-6
> > 
> > Claude assisting to write a one-liner patch? It's becoming ridiculous.
> 
> This patch was generated alongside a set of Maili-related patches and was
> not created specifically on its own.

Okay...

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

-- 
With best wishes
Dmitry

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Krzysztof Kozlowski]

On Mon, May 25, 2026 at 01:08:54PM +0300, Dmitry Baryshkov wrote:
> On Mon, May 25, 2026 at 05:37:23PM +0800, Yijie Yang wrote:
> > 
> > 
> > On 5/25/2026 4:37 PM, Dmitry Baryshkov wrote:
> > > On Mon, May 25, 2026 at 02:21:17PM +0800, Yijie Yang wrote:
> > > > Document compatible string for the FastRPC interface on the Qualcomm Maili
> > > > SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
> > > > fallback to Kaanapali.
> > > 
> > > Can I assume that it has the same bus width as Kaanapali?
> > 
> > Yes, the DMA width for CDSP and ADSP is the same. If you were referring to
> > something other than the DMA width, please let me know.
> 
> Thanks for the confirmation.
> 
> > 
> > > 
> > > > 
> > > > Assisted-by: Claude:claude-opus-4-6
> > > 
> > > Claude assisting to write a one-liner patch? It's becoming ridiculous.
> > 
> > This patch was generated alongside a set of Maili-related patches and was
> > not created specifically on its own.
> 
> Okay...

If a human cannot write and validate this one, I see as putting effort
on maintainers.

Dropping from patchwork.

Best regards,
Krzysztof

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Yijie Yang]

On 5/30/2026 7:20 PM, Krzysztof Kozlowski wrote:
> On Mon, May 25, 2026 at 01:08:54PM +0300, Dmitry Baryshkov wrote:
>> On Mon, May 25, 2026 at 05:37:23PM +0800, Yijie Yang wrote:
>>>
>>>
>>> On 5/25/2026 4:37 PM, Dmitry Baryshkov wrote:
>>>> On Mon, May 25, 2026 at 02:21:17PM +0800, Yijie Yang wrote:
>>>>> Document compatible string for the FastRPC interface on the Qualcomm Maili
>>>>> SoC, which is compatible with the Qualcomm Kaanapali FastRPC and can
>>>>> fallback to Kaanapali.
>>>>
>>>> Can I assume that it has the same bus width as Kaanapali?
>>>
>>> Yes, the DMA width for CDSP and ADSP is the same. If you were referring to
>>> something other than the DMA width, please let me know.
>>
>> Thanks for the confirmation.
>>
>>>
>>>>
>>>>>
>>>>> Assisted-by: Claude:claude-opus-4-6
>>>>
>>>> Claude assisting to write a one-liner patch? It's becoming ridiculous.
>>>
>>> This patch was generated alongside a set of Maili-related patches and was
>>> not created specifically on its own.
>>
>> Okay...
> 
> If a human cannot write and validate this one, I see as putting effort
> on maintainers.
> 
> Dropping from patchwork.

I will write and validate this myself and then remove this tag.

> 
> Best regards,
> Krzysztof
> 

-- 
Best Regards,
Yijie

Re: [PATCH] dt-bindings: misc: qcom,fastrpc: Add Maili FastRPC compatible

[Krzysztof Kozlowski]

On 01/06/2026 03:23, Yijie Yang wrote:
>>>
>>> Okay...
>>
>> If a human cannot write and validate this one, I see as putting effort
>> on maintainers.
>>
>> Dropping from patchwork.
> 
> I will write and validate this myself and then remove this tag.

Upstream maintainer's task is not to review AI generated code, but
review people's code. I have no clue which case is here and
unfortunately I make assumptions, usually in favor of less work for me.

If contributors send us AI code, then basically contributors are proxies
between the AI model and maintainer. I don't want to talk with your AI
through you, I have no such interests (and such process would not
scale). Reviewing AI code does not give me actual pleasure of work - I
have zero emotional connection to such code, no pleasure, I simply do
not care and decide to spend my time on something else.

Whether you actually use AI is a different thing, just like using other
tools, but if a trivial patch is done with AI, I don't believe it was
reviewed by you, because writing it is a similar amount of effort, so
obvious choice for me would be to write it by myself.

Best regards,
Krzysztof