Re: [PATCH v2 12/46] dt-bindings: soc: mediatek: mutex: Allow #trigger-source-cells

On 7/22/26 17:45, Rob Herring wrote:
> On Tue, Jul 14, 2026 at 01:43:40PM +0200, AngeloGioacchino Del Regno wrote:
>> This hardware controls trigger sources, and there's even a generic
>> binding just for that: allow #trigger-source-cells in MuteX, so
>> that this is allowed to provide triggers to external HW.
>>
>> Acked-by: AngeloGioacchino Del Regno <[email protected]>
> 
> You ack-ed your own patch?
> 

Mysterious things happen in my workflow... :facepalm:

>> Signed-off-by: AngeloGioacchino Del Regno <[email protected]>
>> ---
>>   .../devicetree/bindings/soc/mediatek/mediatek,mutex.yaml      | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
>> index 5267cfe92572..886e6f904b78 100644
>> --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
>> +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
>> @@ -54,6 +54,9 @@ properties:
>>       items:
>>         - description: MUTEX Clock
>>   
>> +  '#trigger-source-cells':
>> +    const: 1
>> +
>>     mediatek,gce-events:
>>       description:
>>         The event id which is mapping to the specific hardware event signal
>> @@ -116,6 +119,7 @@ examples:
>>               interrupts = <GIC_SPI 169 IRQ_TYPE_LEVEL_LOW>;
>>               power-domains = <&spm MT8173_POWER_DOMAIN_MM>;
>>               clocks = <&mmsys CLK_MM_MUTEX_32K>;
>> +            #trigger-source-cells = <1>;
>>               mediatek,gce-events = <CMDQ_EVENT_MUTEX0_STREAM_EOF>,
>>                                     <CMDQ_EVENT_MUTEX1_STREAM_EOF>;
>>           };
>> -- 
>> 2.54.0
>>