linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: CK Hu <ck.hu@mediatek.com>
To: jason-jh.lin <jason-jh.lin@mediatek.com>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	"Chun-Kuang Hu" <chunkuang.hu@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	<hsinyi@chromium.org>, <fshao@chromium.org>,
	<moudy.ho@mediatek.com>, <roy-cw.yeh@mediatek.com>,
	Fabien Parent <fparent@baylibre.com>, <nancy.lin@mediatek.com>,
	<singo.chang@mediatek.com>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	 <linux-kernel@vger.kernel.org>,
	<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH v16 3/8] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding
Date: Fri, 18 Mar 2022 14:43:04 +0800	[thread overview]
Message-ID: <1daa3b8dabb97017d0f92437a81b250f8375544c.camel@mediatek.com> (raw)
In-Reply-To: <20220307032859.3275-4-jason-jh.lin@mediatek.com>

Hi, Jason:

On Mon, 2022-03-07 at 11:28 +0800, jason-jh.lin wrote:
> There are 2 mmsys, namely vdosys0 and vdosys1 in mt8195.
> Each of them is bound to a display pipeline, so add their
> definition in mtk-mmsys documentation with 2 compatibles.

Could one vdosys be union of vdosys0 and vdosys1? In MT8173, one mmsys
support multiple pipeline. Describe more in commit message to support
that two vdosys are necessary.

Regards,
CK

> 
> Signed-off-by: jason-jh.lin <jason-jh.lin@mediatek.com>
> ---
>  .../devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml        | 2
> ++
>  1 file changed, 2 insertions(+)
> 
> diff --git
> a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> index 6c2c3edcd443..c5ba515cb0d7 100644
> ---
> a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> +++
> b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> @@ -32,6 +32,8 @@ properties:
>                - mediatek,mt8186-mmsys
>                - mediatek,mt8192-mmsys
>                - mediatek,mt8365-mmsys
> +              - mediatek,mt8195-vdosys0
> +              - mediatek,mt8195-vdosys1
>            - const: syscon
>        - items:
>            - const: mediatek,mt7623-mmsys


_______________________________________________
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-18  6:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  3:28 [PATCH v16 0/8] Add Mediatek Soc DRM (vdosys0) support for mt8195 jason-jh.lin
2022-03-07  3:28 ` [PATCH v16 1/8] dt-bindings: soc: mediatek: move out common module from display folder jason-jh.lin
2022-03-07 10:04   ` AngeloGioacchino Del Regno
2022-03-07  3:28 ` [PATCH v16 2/8] dt-bindings: arm: mediatek: mmsys: add power and gce properties jason-jh.lin
2022-03-07 10:05   ` AngeloGioacchino Del Regno
2022-03-18  5:14   ` CK Hu
2022-03-31 11:09   ` Matthias Brugger
2022-03-07  3:28 ` [PATCH v16 3/8] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding jason-jh.lin
2022-03-07 10:04   ` AngeloGioacchino Del Regno
2022-03-18  6:43   ` CK Hu [this message]
2022-03-28  3:29     ` Jason-JH Lin
2022-03-07  3:28 ` [PATCH v16 4/8] soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 jason-jh.lin
2022-03-07  4:33   ` Fei Shao
2022-03-18  7:02   ` CK Hu
2022-03-28  5:03   ` Jason-JH Lin
2022-03-28  5:39     ` CK Hu
2022-03-30 10:04       ` Jason-JH Lin
2022-03-31 11:01         ` Matthias Brugger
2022-03-31 15:40           ` Jason-JH Lin
2022-03-07  3:28 ` [PATCH v16 5/8] soc: mediatek: add mtk-mutex " jason-jh.lin
2022-03-07  4:34   ` Fei Shao
2022-03-18  7:21   ` CK Hu
2022-03-28  4:45     ` Jason-JH Lin
2022-03-28  5:35       ` CK Hu
2022-03-31  1:44     ` Jason-JH Lin
2022-03-07  3:28 ` [PATCH v16 6/8] drm/mediatek: add DSC support for mediatek-drm jason-jh.lin
2022-03-07  3:28 ` [PATCH v16 7/8] drm/mediatek: add MERGE " jason-jh.lin
2022-03-07  3:28 ` [PATCH v16 8/8] drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 jason-jh.lin

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=1daa3b8dabb97017d0f92437a81b250f8375544c.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@foss.st.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=enric.balletbo@collabora.com \
    --cc=fparent@baylibre.com \
    --cc=fshao@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=jason-jh.lin@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=moudy.ho@mediatek.com \
    --cc=nancy.lin@mediatek.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=roy-cw.yeh@mediatek.com \
    --cc=singo.chang@mediatek.com \
    /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).