dt-bindings: mediatek: Add optional mediatek,gce-events property

This property is used by gce clients.

Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
Acked-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20210622030741.2120393-2-hsinyi@chromium.org
Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>

diff --git a/Documentation/devicetree/bindings/mailbox/mtk-gce.txt b/Documentation/devicetree/bindings/mailbox/mtk-gce.txt
index 7771ecaac58683a68bd2a6bb03deb1b6b4b486e4..2ef7ff67cb2b0cd0d451b1f3e2a3a04e43240fe1 100644 (file)
--- a/Documentation/devicetree/bindings/mailbox/mtk-gce.txt
+++ b/Documentation/devicetree/bindings/mailbox/mtk-gce.txt
@@ -35,6 +35,10 @@ Optional properties for a client device:
   start_offset: the start offset of register address that GCE can access.
   size: the total size of register address that GCE can access.
 
+Optional properties for a client mutex node:
+- mediatek,gce-events: GCE events used by clients. The event numbers are
+  defined in 'dt-bindings/gce/<chip>-gce.h'.
+
 Some vaules of properties are defined in 'dt-bindings/gce/mt8173-gce.h',
 'dt-binding/gce/mt8183-gce.h' or 'dt-bindings/gce/mt6779-gce.h'. Such as
 sub-system ids, thread priority, event ids.
@@ -62,3 +66,14 @@ Example for a client device:
                                          <&gce SUBSYS_1401XXXX 0x2000 0x100>;
                ...
        };
+
+Example for a client mutex node:
+       mutex: mutex@14020000 {
+               compatible = "mediatek,mt8173-disp-mutex";
+               reg = <0 0x14020000 0 0x1000>;
+               interrupts = <GIC_SPI 169 IRQ_TYPE_LEVEL_LOW>;
+               power-domains = <&scpsys MT8173_POWER_DOMAIN_MM>;
+               clocks = <&mmsys CLK_MM_MUTEX_32K>;
+               mediatek,gce-events = <CMDQ_EVENT_MUTEX0_STREAM_EOF>,
+                                     <CMDQ_EVENT_MUTEX1_STREAM_EOF>;
+       };