Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wilczynski <m.wilczynski@samsung.com>
To: Icenowy Zheng <zhengxingda@iscas.ac.cn>,
	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>,
	Drew Fustini <fustini@kernel.org>, Guo Ren <guoren@kernel.org>,
	Fu Wei <wefu@redhat.com>, Philipp Zabel <p.zabel@pengutronix.de>,
	Heiko Stuebner <heiko@sntech.de>,
	Andrzej Hajda <andrzej.hajda@intel.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Robert Foss <rfoss@kernel.org>,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Jernej Skrabec <jernej.skrabec@gmail.com>
Cc: Han Gao <rabenda.cn@gmail.com>, Yao Zi <ziyao@disroot.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v4 0/9] Verisilicon DC8200 driver (and adaption to TH1520)
Date: Mon, 29 Dec 2025 17:32:03 +0100	[thread overview]
Message-ID: <a1d2fc77-ac57-49d4-a13e-cc391e6e2b92@samsung.com> (raw)
In-Reply-To: <20251224161205.1132149-1-zhengxingda@iscas.ac.cn>



On 12/24/25 17:11, Icenowy Zheng wrote:
> This patchset tries to add a driver for Verisilicon DC8200 driver, and
> demonstrates the driver on T-Head TH1520 with its HDMI output.
> 
> This display controller IP is used on StarFive JH7110 too, but as the
> HDMI controller used there isn't as common as the DesignWare one, I
> choose to use TH1520 in this patchset.
> 
> The DC driver is written with other DC-series (mainly DC8000, which is
> known to be used on Eswin EIC7700 SoC) display controllers in mind, and
> uses the identification registers available on all Vivante branded IPs.
> A known exception is DCNano display controller, which is unlikely to be
> supported by this driver because of totally different register map and
> no known identification registers. (P.S. the in-tree loongson DRM driver
> seems to be for some DCNano instances based on the register map.)
> 
> The HDMI controller seems to come with some common PHY by Synopsys, the
> DesignWare HDMI TX 2.0 PHY. By searching a few register names from the
> BSP driver of that PHY, that PHY seems to be used by a in-tree dw-hdmi
> glue, rcar_dw_hdmi -- an updated downstream version of rcar_dw_hdmi
> contains all 6 registers set here in the th1520-dw-hdmi driver. Some
> more suprising thing is that RK3288 uses the same PHY too, but the
> in-tree dw_hdmi-rockchip driver writes the configuration data array in a
> weird way to reuse the HDMI 3D TX PHY configuring function. It might be
> valuable to add common configuring function and configuration data
> definition for this HDMI 2.0 PHY too, but the current driver in this
> patchset simply duplicated most configuration logic from rcar_dw_hdmi
> driver (but with 3 extra configuration registers configured).
> 
> Icenowy Zheng (9):
>   dt-bindings: vendor-prefixes: add verisilicon
>   dt-bindings: display: add verisilicon,dc
>   drm: verisilicon: add a driver for Verisilicon display controllers
>   dt-bindings: display/bridge: add binding for TH1520 HDMI controller
>   drm/bridge: add a driver for T-Head TH1520 HDMI controller
>   riscv: dts: thead: add DPU and HDMI device tree nodes
>   riscv: dts: thead: lichee-pi-4a: enable HDMI
>   MAINTAINERS: assign myself as maintainer for verisilicon DC driver
>   mailmap: map all Icenowy Zheng's mail addresses
> 

I tested this patchset on the Lichee Pi 4A (TH1520). I successfully ran a 
fully hardware accelerated graphics stack using Weston and Zink over the 
HDMI output.

I have documented the reproduction steps and test results here:
[1] https://mwilczynski.dev/posts/riscv-gpu-zink/#building-the-stack-reproduction-guide

Great work, thank you!

Feel free to add to driver and DTS patches (3,5,6,7).
Tested-by: Michal Wilczynski <m.wilczynski@samsung.com>

Best regards,
-- 
Michal Wilczynski <m.wilczynski@samsung.com>

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

      parent reply	other threads:[~2025-12-29 16:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20251224161255eucas1p24c6de486b021f25007ed1ce24468cab2@eucas1p2.samsung.com>
2025-12-24 16:11 ` [PATCH v4 0/9] Verisilicon DC8200 driver (and adaption to TH1520) Icenowy Zheng
2025-12-24 16:11   ` [PATCH v4 1/9] dt-bindings: vendor-prefixes: add verisilicon Icenowy Zheng
2025-12-24 16:11   ` [PATCH v4 2/9] dt-bindings: display: add verisilicon,dc Icenowy Zheng
2025-12-25  9:35     ` Han Gao (Revy)
2025-12-27 11:08       ` Krzysztof Kozlowski
2025-12-25  9:45     ` Han Gao (Revy)
2025-12-27 11:09       ` Krzysztof Kozlowski
2025-12-27 12:08         ` Han Gao
2025-12-28  7:48           ` Krzysztof Kozlowski
2025-12-28  7:54             ` Han Gao
2026-01-05 15:46     ` Rob Herring
2026-01-05 16:11       ` Icenowy Zheng
2026-01-05 16:20         ` Rob Herring
2026-01-13 13:41           ` Icenowy Zheng
2025-12-24 16:11   ` [PATCH v4 3/9] drm: verisilicon: add a driver for Verisilicon display controllers Icenowy Zheng
2025-12-25  9:36     ` Han Gao (Revy)
2025-12-25  9:45     ` Han Gao (Revy)
2025-12-31 14:20     ` Luca Ceresoli
2025-12-24 16:12   ` [PATCH v4 4/9] dt-bindings: display/bridge: add binding for TH1520 HDMI controller Icenowy Zheng
2025-12-24 16:12   ` [PATCH v4 5/9] drm/bridge: add a driver for T-Head " Icenowy Zheng
2025-12-25  9:46     ` Han Gao (Revy)
2025-12-25 11:07     ` Andy Yan
2025-12-26 13:27       ` [PATCH " Icenowy Zheng
2025-12-27  7:03         ` Andy Yan
2025-12-27  7:22           ` Icenowy Zheng
2025-12-28 17:41             ` Heiko Stübner
2025-12-24 16:12   ` [PATCH v4 6/9] riscv: dts: thead: add DPU and HDMI device tree nodes Icenowy Zheng
2025-12-25  9:46     ` Han Gao (Revy)
2025-12-24 16:12   ` [PATCH v4 7/9] riscv: dts: thead: lichee-pi-4a: enable HDMI Icenowy Zheng
2025-12-25  9:47     ` Han Gao (Revy)
2025-12-24 16:12   ` [PATCH v4 8/9] MAINTAINERS: assign myself as maintainer for verisilicon DC driver Icenowy Zheng
2025-12-24 16:12   ` [PATCH v4 9/9] mailmap: map all Icenowy Zheng's mail addresses Icenowy Zheng
2025-12-29 16:32   ` Michal Wilczynski [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=a1d2fc77-ac57-49d4-a13e-cc391e6e2b92@samsung.com \
    --to=m.wilczynski@samsung.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fustini@kernel.org \
    --cc=guoren@kernel.org \
    --cc=heiko@sntech.de \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=rabenda.cn@gmail.com \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=wefu@redhat.com \
    --cc=zhengxingda@iscas.ac.cn \
    --cc=ziyao@disroot.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