From: Jason-JH Lin <jason-jh.lin@mediatek.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.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>, <fshao@chromium.org>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
<hsinyi@chromium.org>, Yongqiang Niu <yongqiang.niu@mediatek.com>,
<nancy.lin@mediatek.com>, <singo.chang@mediatek.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v5 0/6] Add Mediatek Soc DRM (vdosys0) support for mt8195
Date: Tue, 3 Aug 2021 10:24:13 +0800 [thread overview]
Message-ID: <a18c9073b5dec59a4bdb3253dbc75dd56763da47.camel@mediatek.com> (raw)
In-Reply-To: <a8ce9da7-21c2-f9ef-161a-647d3f8748f3@collabora.com>
Hi Enric,
On Fri, 2021-07-30 at 13:45 +0200, Enric Balletbo i Serra wrote:
> Hi Jason,
>
> Thank you for your patch.
>
> On 29/7/21 19:07, jason-jh.lin wrote:
> > The hardware path of vdosys0 with eDP panel output need to go
> > through
> > by several modules, such as, OVL, RDMA, COLOR, CCORR, AAL, GAMMA,
> > DITHER, DSC and MERGE.
> >
>
>
> You said in other discussions that vdosys0 has eDP panel output and
> vdosys1 has
> DP output. Is it possible to switch the outputs? What I am wondering
> is if this
> configuration is hardware specific or board specific, i.e it'll be
> possible to
> have another board that has DP output on vdosys0 and eDP output for
> vdosys1?
>
> Thanks,
> Enric
>
Because the configuration is hardware specific in mt8195 SoC, it is
possible to switch the output to DP or HDMI for vdosys1 and to switch
the output to DSI or eDP for vdosys0.
Due to the hot plug reqirement for HDMI and DP, vdosys1 will support
runtime sitching output. vdosys0 can do that too, but there is no hot
plug requirement for DSI panel or eDP panel.
So we configure the output to eDP for vdosys0 in build time currently.
In another board, such as mt8173 SoC, it doesn't have vdosys1 but it is
able to set the output to DSI and HDMI for vdosys0 at the same time.
Regards,
Jason-JH.Lin
>
> > Change in v5:
> > - add power-domain property into vdosys0 and vdosys1 dts node.
> > - add MT8195 prifix and remove unused VDO1 define in mt8195-mmsys.h
> >
> > Change in v4:
> > - extract dt-binding patches to another patch series
> >
> > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-mediatek/list/?series=519597__;!!CTRNKA9wMg0ARbw!3juKPT3EahvXs9aSRTDPxQfapIiXFGGx996Kss9b8DITyA19pd5F4K0AWsEp1U3C3FSl$
> >
> > - squash DSC module into mtk_drm_ddp_comp.c
> > - add coment and simplify MERGE config function
> >
> > Change in v3:
> > - change mmsys and display dt-bindings document from txt to yaml
> > - add MERGE additional description in display dt-bindings document
> > - fix mboxes-cells number of vdosys0 node in dts
> > - drop mutex eof convert define
> > - remove pm_runtime apis in DSC and MERGE
> > - change DSC and MERGE enum to alphabetic order
> >
> > Change in v2:
> > - add DSC yaml file
> > - add mt8195 drm driver porting parts in to one patch
> > - remove useless define, variable, structure member and function
> > - simplify DSC and MERGE file and switch threre order
> >
> > jason-jh.lin (6):
> > arm64: dts: mt8195: add display node for vdosys0
> > soc: mediatek: add mtk-mmsys support for mt8195 vdosys0
> > soc: mediatek: add mtk-mutex support for mt8195 vdosys0
> > drm/mediatek: add mediatek-drm of vdosys0 support for mt8195
> > drm/mediatek: add DSC support for mt8195
> > drm/mediatek: add MERGE support for mt8195
> >
> > arch/arm64/boot/dts/mediatek/mt8195.dtsi | 112 ++++++++
> > drivers/gpu/drm/mediatek/Makefile | 1 +
> > drivers/gpu/drm/mediatek/mtk_disp_drv.h | 8 +
> > drivers/gpu/drm/mediatek/mtk_disp_merge.c | 277
> > ++++++++++++++++++++
> > drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 6 +
> > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 62 +++++
> > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.h | 2 +
> > drivers/gpu/drm/mediatek/mtk_drm_drv.c | 32 ++-
> > drivers/gpu/drm/mediatek/mtk_drm_drv.h | 1 +
> > drivers/soc/mediatek/mt8195-mmsys.h | 96 +++++++
> > drivers/soc/mediatek/mtk-mmsys.c | 11 +
> > drivers/soc/mediatek/mtk-mutex.c | 93 ++++++-
> > include/linux/soc/mediatek/mtk-mmsys.h | 9 +
> > 13 files changed, 706 insertions(+), 4 deletions(-)
> > create mode 100644 drivers/gpu/drm/mediatek/mtk_disp_merge.c
> > create mode 100644 drivers/soc/mediatek/mt8195-mmsys.h
> >
--
Jason-JH Lin <jason-jh.lin@mediatek.com>
prev parent reply other threads:[~2021-08-03 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 17:07 [PATCH v5 0/6] Add Mediatek Soc DRM (vdosys0) support for mt8195 jason-jh.lin
2021-07-29 17:07 ` [PATCH v5 1/6] arm64: dts: mt8195: add display node for vdosys0 jason-jh.lin
2021-08-01 0:36 ` Chun-Kuang Hu
2021-08-03 16:11 ` Jason-JH Lin
2021-07-29 17:07 ` [PATCH v5 2/6] soc: mediatek: add mtk-mmsys support for mt8195 vdosys0 jason-jh.lin
2021-07-30 11:41 ` Enric Balletbo i Serra
2021-08-03 2:30 ` Jason-JH Lin
2021-07-29 17:07 ` [PATCH v5 3/6] soc: mediatek: add mtk-mutex " jason-jh.lin
2021-07-29 17:07 ` [PATCH v5 4/6] drm/mediatek: add mediatek-drm of vdosys0 support for mt8195 jason-jh.lin
2021-07-29 17:07 ` [PATCH v5 5/6] drm/mediatek: add DSC " jason-jh.lin
2021-07-30 23:11 ` Chun-Kuang Hu
2021-08-05 20:54 ` Jason-JH Lin
2021-07-29 17:07 ` [PATCH v5 6/6] drm/mediatek: add MERGE " jason-jh.lin
2021-08-01 0:33 ` Chun-Kuang Hu
2021-08-05 21:04 ` Jason-JH Lin
2021-07-30 11:45 ` [PATCH v5 0/6] Add Mediatek Soc DRM (vdosys0) " Enric Balletbo i Serra
2021-08-03 2:24 ` Jason-JH Lin [this message]
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=a18c9073b5dec59a4bdb3253dbc75dd56763da47.camel@mediatek.com \
--to=jason-jh.lin@mediatek.com \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=enric.balletbo@collabora.com \
--cc=fshao@chromium.org \
--cc=hsinyi@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nancy.lin@mediatek.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=singo.chang@mediatek.com \
--cc=yongqiang.niu@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