In order to share the same hardware information with MDP3,
change the MUTEX dt-binding to the path "soc/mediatek".
Signed-off-by: Moudy Ho <moudy.ho@xxxxxxxxxxxx>
---
.../{display => soc}/mediatek/mediatek,mutex.yaml | 10 +++-------
1 file changed, 3 insertions(+), 7 deletions(-)
rename Documentation/devicetree/bindings/{display => soc}/mediatek/mediatek,mutex.yaml (84%)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
similarity index 84%
rename from Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.yaml
rename to Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
index 6eca525eced0..4adc67cafd29 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.yaml
+++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
-$id: http://devicetree.org/schemas/display/mediatek/mediatek,mutex.yaml#
+$id: http://devicetree.org/schemas/soc/mediatek/mediatek,mutex.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Mediatek mutex
@@ -9,17 +9,13 @@ title: Mediatek mutex
maintainers:
- Chun-Kuang Hu <chunkuang.hu@xxxxxxxxxx>
- Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
+ - Matthias Brugger <matthias.bgg@xxxxxxxxx>
description: |
Mediatek mutex, namely MUTEX, is used to send the triggers signals called
- Start Of Frame (SOF) / End Of Frame (EOF) to each sub-modules on the display
- data path or MDP data path.
+ Start Of Frame(SOF) / End Of Frame(EOF) to each sub-modules on the data path.
In some SoC, such as mt2701, MUTEX could be a hardware mutex which protects
the shadow register.
- MUTEX device node must be siblings to the central MMSYS_CONFIG node.
- For a description of the MMSYS_CONFIG binding, see
- Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
- for details.
properties:
compatible:
--
2.18.0
