linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: CK Hu <ck.hu@mediatek.com>
To: Moudy Ho <moudy.ho@mediatek.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	"Jernej Skrabec" <jernej.skrabec@siol.net>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Rob Landley <rob@landley.net>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Alexandre Courbot <acourbot@chromium.org>, <tfiga@chromium.org>,
	<drinkcat@chromium.org>, <pihsun@chromium.org>,
	<hsinyi@google.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Maoguang Meng <maoguang.meng@mediatek.com>,
	daoyuan huang <daoyuan.huang@mediatek.com>,
	Ping-Hsun Wu <ping-hsun.wu@mediatek.com>,
	<menghui.lin@mediatek.com>, <sj.huang@mediatek.com>,
	<allen-kh.cheng@mediatek.com>, <randy.wu@mediatek.com>,
	<jason-jh.lin@mediatek.com>, <roy-cw.yeh@mediatek.com>,
	<river.cheng@mediatek.com>, <srv_heupstream@mediatek.com>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v13 3/6] dt-bindings: soc: mediatek: move out common module from display folder
Date: Wed, 16 Mar 2022 11:36:04 +0800	[thread overview]
Message-ID: <7c93cb5e09153007589b8f90ad22af6a03f8a726.camel@mediatek.com> (raw)
In-Reply-To: <20220315061031.21642-4-moudy.ho@mediatek.com>

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:


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-03-16  3:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  6:10 [PATCH v13 0/6] Add mutex support for MDP Moudy Ho
2022-03-15  6:10 ` [PATCH v13 1/6] soc: mediatek: mutex: add common interface to accommodate multiple modules operationg MUTEX Moudy Ho
2022-03-15  9:10   ` AngeloGioacchino Del Regno
2022-03-15 14:41     ` Rob Landley
2022-03-15 14:50       ` Geert Uytterhoeven
2022-03-15 14:58         ` AngeloGioacchino Del Regno
2022-03-17 12:43           ` moudy.ho
2022-03-16  2:25   ` CK Hu
2022-03-17 12:45     ` moudy.ho
2022-03-15  6:10 ` [PATCH v13 2/6] soc: mediatek: mutex: add 8183 MUTEX MOD settings for MDP Moudy Ho
2022-03-15  9:11   ` AngeloGioacchino Del Regno
2022-03-16  3:31   ` CK Hu
2022-03-17 10:11     ` moudy.ho
2022-03-15  6:10 ` [PATCH v13 3/6] dt-bindings: soc: mediatek: move out common module from display folder Moudy Ho
2022-03-15  9:11   ` AngeloGioacchino Del Regno
2022-03-16  3:36   ` CK Hu [this message]
2022-03-15  6:10 ` [PATCH v13 4/6] dt-bindings: soc: mediatek: add gce-client-reg for MUTEX Moudy Ho
2022-03-15  9:12   ` AngeloGioacchino Del Regno
2022-03-16  3:50   ` CK Hu
2022-03-15  6:10 ` [PATCH v13 5/6] dts: arm64: mt8183: add GCE client property for Mediatek MUTEX Moudy Ho
2022-03-15  9:12   ` AngeloGioacchino Del Regno
2022-03-15  6:10 ` [PATCH v13 6/6] soc: mediatek: mutex: add functions that operate registers by CMDQ Moudy Ho
2022-03-15  9:13   ` AngeloGioacchino Del Regno
2022-03-17  3:39   ` CK Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7c93cb5e09153007589b8f90ad22af6a03f8a726.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=acourbot@chromium.org \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=daoyuan.huang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=geert+renesas@glider.be \
    --cc=hsinyi@google.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jason-jh.lin@mediatek.com \
    --cc=jernej.skrabec@siol.net \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=maoguang.meng@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=menghui.lin@mediatek.com \
    --cc=moudy.ho@mediatek.com \
    --cc=pihsun@chromium.org \
    --cc=ping-hsun.wu@mediatek.com \
    --cc=randy.wu@mediatek.com \
    --cc=river.cheng@mediatek.com \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=roy-cw.yeh@mediatek.com \
    --cc=sj.huang@mediatek.com \
    --cc=srv_heupstream@mediatek.com \
    --cc=tfiga@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).