From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Luca Leonardo Scorcia <l.scorcia@gmail.com>,
linux-mediatek@lists.infradead.org
Cc: 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>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
CK Hu <ck.hu@mediatek.com>, Jitao shi <jitao.shi@mediatek.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Add support for the mt8167 display pipeline
Date: Mon, 21 Sep 2026 12:19:57 +0200 [thread overview]
Message-ID: <e1ee74fc-6cbe-4b72-93ba-3da830ee62f5@collabora.com> (raw)
In-Reply-To: <20260918175736.355305-1-l.scorcia@gmail.com>
On 9/18/26 19:55, Luca Leonardo Scorcia wrote:
> This series adds support for (almost) all display blocks of mt8167.
> This SoC supports a DSI or DPI display and has HDMI output via a second
> DPI block wired to the HDMI phy.
>
> All the hard work was already upstreamed in the past, now all that's left
> is some glue. In the first two patches we add support for the DPI output
> blocks. In the third one we describe all the possible combinations of the
> SoC display pipeline and in the last one we add the required nodes to the
> SoC dtsi.
>
> The final outputs of the display pipeline in the SoC dtsi are
> intentionally left not connected to allow board dts to specify their
> own output node.
>
> I said almost all display blocks because HDMI output is not included in
> this patch. I have it tested and working at all supported resolutions, but
> since it needs some fixes in clocks and a new phy driver, I will send it
> in a separate series.
>
> The series has been tested on a Lenovo Smart Clock 2 (DSI), a Xiaomi Mi
> Smart Clock 2 (DSI), and a Sony Playstation Classic Mini (HDMI via DPI).
> Unfortunately I couldn't find an actual device using a DPI display, but
I don't think that it even exists with your SoC. It's fine though, because
you're anyway testing the DPI interface in one way or another.
> since DPI1-HDMI works, I feel confident saying that the clocks divisors
> are correct.
While series is
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>
> Luca Leonardo Scorcia (4):
> dt-bindings: display: mediatek: dpi: Add compatible for mt8167
> drm/mediatek: Add support for mt8167 Digital Parallel Interface
> soc: mediatek: mt8167-mmsys: add routes for all display paths
> arm64: dts: mediatek: mt8167: Add DRM nodes
>
> .../display/mediatek/mediatek,dpi.yaml | 1 +
> arch/arm64/boot/dts/mediatek/mt8167.dtsi | 369 ++++++++++++++++++
> drivers/gpu/drm/mediatek/mtk_dpi.c | 23 ++
> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 2 +
> drivers/soc/mediatek/mt8167-mmsys.h | 183 ++++++++-
> 5 files changed, 569 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2026-09-21 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 17:55 Luca Leonardo Scorcia
2026-09-18 17:55 ` [PATCH 1/4] dt-bindings: display: mediatek: dpi: Add compatible for mt8167 Luca Leonardo Scorcia
2026-09-18 17:55 ` [PATCH 2/4] drm/mediatek: Add support for mt8167 Digital Parallel Interface Luca Leonardo Scorcia
2026-09-18 17:55 ` [PATCH 3/4] soc: mediatek: mt8167-mmsys: add routes for all display paths Luca Leonardo Scorcia
2026-09-18 18:29 ` Luca Leonardo Scorcia
2026-09-18 17:55 ` [PATCH 4/4] arm64: dts: mediatek: mt8167: Add DRM nodes Luca Leonardo Scorcia
2026-09-21 10:19 ` AngeloGioacchino Del Regno [this message]
2026-09-21 10:21 ` (subset) [PATCH 0/4] Add support for the mt8167 display pipeline AngeloGioacchino Del Regno
2026-09-21 10:36 ` Luca Leonardo Scorcia
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=e1ee74fc-6cbe-4b72-93ba-3da830ee62f5@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@gmail.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=l.scorcia@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@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@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®