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