diff mbox series

[v13,3/6] dt-bindings: soc: mediatek: move out common module from display folder

Message ID 20220315061031.21642-4-moudy.ho@mediatek.com (mailing list archive)
State New, archived
Headers show
Series Add mutex support for MDP | expand

Commit Message

Moudy Ho March 15, 2022, 6:10 a.m. UTC
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@mediatek.com>
---
 .../{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%)

Comments

AngeloGioacchino Del Regno March 15, 2022, 9:11 a.m. UTC | #1
Il 15/03/22 07:10, Moudy Ho ha scritto:
> 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@mediatek.com>

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
CK Hu (胡俊光) March 16, 2022, 3:36 a.m. UTC | #2
Hi, Moudy:

On Tue, 2022-03-15 at 14:10 +0800, Moudy Ho wrote:
> 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@mediatek.com>
> ---
>  .../{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.y
> aml
> b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
> similarity index 84%
> rename from
> Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.yam
> l
> rename to
> Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
> index 6eca525eced0..4adc67cafd29 100644
> ---
> a/Documentation/devicetree/bindings/display/mediatek/mediatek,mutex.y
> aml
> +++
> 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: 
> https://urldefense.com/v3/__http://devicetree.org/schemas/display/mediatek/mediatek,mutex.yaml*__;Iw!!CTRNKA9wMg0ARbw!wGUhdDCs1gqW3Mb5paZPaF-qpdK0BBiR6-zMnprFhfu_YiYLf4vEbi1fE1ktpA$
>  
> +$id: 
> https://urldefense.com/v3/__http://devicetree.org/schemas/soc/mediatek/mediatek,mutex.yaml*__;Iw!!CTRNKA9wMg0ARbw!wGUhdDCs1gqW3Mb5paZPaF-qpdK0BBiR6-zMnprFhfu_YiYLf4vEbi0c8j0j1A$
>  
>  $schema: 
> https://urldefense.com/v3/__http://devicetree.org/meta-schemas/core.yaml*__;Iw!!CTRNKA9wMg0ARbw!wGUhdDCs1gqW3Mb5paZPaF-qpdK0BBiR6-zMnprFhfu_YiYLf4vEbi2jwnYkJA$
>  
>  
>  title: Mediatek mutex
> @@ -9,17 +9,13 @@ title: Mediatek mutex
>  maintainers:
>    - Chun-Kuang Hu <chunkuang.hu@kernel.org>
>    - Philipp Zabel <p.zabel@pengutronix.de>
> +  - Matthias Brugger <matthias.bgg@gmail.com>
>  
>  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.

If this is not related to 'move out', separate this to another patch.

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

If this is not related to 'move out', separate this to another patch.

Regards,
CK

>  
>  properties:
>    compatible:
diff mbox series

Patch

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@kernel.org>
   - Philipp Zabel <p.zabel@pengutronix.de>
+  - Matthias Brugger <matthias.bgg@gmail.com>
 
 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: