Hi, Moudy: On Tue, 2022-03-15 at 14:10 +0800, Moudy Ho wrote: > In order to allow modules with latency requirements such as MDP3 > to set registers through CMDQ, add the relevant GCE property. Reviewed-by: CK Hu <ck.hu@xxxxxxxxxxxx> > > Signed-off-by: Moudy Ho <moudy.ho@xxxxxxxxxxxx> > --- > .../devicetree/bindings/soc/mediatek/mediatek,mutex.yaml | 8 > ++++++++ > 1 file changed, 8 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml > b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml > index 4adc67cafd29..06106779d129 100644 > --- > a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml > +++ > b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml > @@ -56,6 +56,14 @@ properties: > include/dt-bindings/gce/<chip>-gce.h of each chips. > $ref: /schemas/types.yaml#/definitions/phandle-array > > + mediatek,gce-client-reg: > + description: The register of client driver can be configured by > gce with > + 4 arguments defined in this property, such as phandle of gce, > subsys id, > + register offset and size. Each GCE subsys id is mapping to a > client > + defined in the header include/dt-bindings/gce/<chip>-gce.h. > + $ref: /schemas/types.yaml#/definitions/phandle-array > + maxItems: 1 > + > required: > - compatible > - reg
