From: Michael Walle <mwalle@kernel.org>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jitao Shi <jitao.shi@mediatek.com>,
Xinlei Lee <xinlei.lee@mediatek.com>
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH 4/4] drm/mediatek: support the DSI0 output on the MT8195 VDOSYS0
Date: Thu, 30 Nov 2023 13:47:17 +0100 [thread overview]
Message-ID: <2d1bae2239626cb51977bf0803cec602@kernel.org> (raw)
In-Reply-To: <20231123133749.2030661-5-mwalle@kernel.org>
> With the latest dynamic selection of the output component, we can now
> support different outputs. Move current output component into the
> dynamic routes array and add the new DSI0 output.
>
> Signed-off-by: Michael Walle <mwalle@kernel.org>
> ---
> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> index 2b0c35cacbc6..6fa88976376e 100644
> --- a/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> +++ b/drivers/gpu/drm/mediatek/mtk_drm_drv.c
> @@ -222,7 +222,11 @@ static const unsigned int mt8195_mtk_ddp_main[] =
> {
> DDP_COMPONENT_DITHER0,
> DDP_COMPONENT_DSC0,
> DDP_COMPONENT_MERGE0,
> - DDP_COMPONENT_DP_INTF0,
Please disregard this patch (the others are ok). There must gone
something
wrong during my testing. DDP_COMPONENT_MERGE0 won't work with
DDP_COMPONENT_DSI0. If anyone has more insights, I'm all ears.
-michael
> +};
> +
> +static const struct mtk_drm_route mt8195_mtk_ddp_main_routes[] = {
> + { 0, DDP_COMPONENT_DP_INTF0 },
> + { 0, DDP_COMPONENT_DSI0 },
> };
>
> static const unsigned int mt8195_mtk_ddp_ext[] = {
> @@ -308,6 +312,8 @@ static const struct mtk_mmsys_driver_data
> mt8192_mmsys_driver_data = {
> static const struct mtk_mmsys_driver_data mt8195_vdosys0_driver_data =
> {
> .main_path = mt8195_mtk_ddp_main,
> .main_len = ARRAY_SIZE(mt8195_mtk_ddp_main),
> + .conn_routes = mt8195_mtk_ddp_main_routes,
> + .num_conn_routes = ARRAY_SIZE(mt8195_mtk_ddp_main_routes),
> .mmsys_dev_num = 2,
> };
next prev parent reply other threads:[~2023-11-30 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 13:37 [PATCH 0/4] drm/mediatek: support DSI output on MT8195 Michael Walle
2023-11-23 13:37 ` [PATCH 1/4] dt-bindings: display: mediatek: dsi: add compatible for MediaTek MT8195 Michael Walle
2023-11-23 17:18 ` Conor Dooley
2023-11-27 13:27 ` AngeloGioacchino Del Regno
2023-11-23 13:37 ` [PATCH 2/4] dt-bindings: phy: add compatible for Mediatek MT8195 Michael Walle
2023-11-23 17:18 ` Conor Dooley
2023-11-23 13:37 ` [PATCH 3/4] arm64: dts: mediatek: mt8195: add DSI and MIPI DPHY nodes Michael Walle
2023-11-24 3:44 ` Chen-Yu Tsai
2023-11-27 13:27 ` AngeloGioacchino Del Regno
2023-11-23 13:37 ` [PATCH 4/4] drm/mediatek: support the DSI0 output on the MT8195 VDOSYS0 Michael Walle
2023-11-27 13:27 ` AngeloGioacchino Del Regno
2023-11-30 12:47 ` Michael Walle [this message]
2023-12-01 9:22 ` AngeloGioacchino Del Regno
2023-11-27 13:22 ` (subset) [PATCH 0/4] drm/mediatek: support DSI output on MT8195 Vinod Koul
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=2d1bae2239626cb51977bf0803cec602@kernel.org \
--to=mwalle@kernel.org \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
--cc=vkoul@kernel.org \
--cc=xinlei.lee@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).