On 7/1/26 14:20, 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.
Signed-off-by: AngeloGioacchino Del Regno
<[email protected]>
Hey Krzysztof, I noticed you gave your A-b/R-b on the other two bindings commits
but you skipped this.
Did you have any doubts on this one that I may clarify for you, or was it just
that this one slipped through while reviewing?
Cheers,
Angelo
---
.../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 1ba086ad749d..429ea149068e 100644
--- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
+++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
@@ -57,6 +57,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
@@ -119,6 +122,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>;
};
