Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Icenowy Zheng <zhengxingda@iscas.ac.cn>
To: Andy Yan <andyshrk@163.com>
Cc: 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>,
	Michal Wilczynski <m.wilczynski@samsung.com>,
	devicetree@vger.kernel.org, Yao Zi <ziyao@disroot.org>,
	 linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Han Gao <rabenda.cn@gmail.com>,
	linux-riscv@lists.infradead.org
Subject: Re: Re: [PATCH v4 5/9] drm/bridge: add a driver for T-Head TH1520 HDMI controller
Date: Sat, 27 Dec 2025 15:22:05 +0800	[thread overview]
Message-ID: <3b5fd30554f91bcd083b2dc450cdf7fe2fa395e2.camel@iscas.ac.cn> (raw)
In-Reply-To: <5ce9d611.1868.19b5e9e7a61.Coremail.andyshrk@163.com>

在 2025-12-27星期六的 15:03 +0800,Andy Yan写道:
> 
> 
> Hello,
> 
> 在 2025-12-26 21:27:53,"Icenowy Zheng" <zhengxingda@iscas.ac.cn> 写道:
> > 在 2025-12-25星期四的 19:07 +0800,Andy Yan写道:
> > > 
> > > 
> > > Hello Icenowy:
> > > 
> > > At 2025-12-25 00:12:01, "Icenowy Zheng" <zhengxingda@iscas.ac.cn>
> > > wrote:
> > > > From: Icenowy Zheng <uwu@icenowy.me>
> > > > 
> > > > T-Head TH1520 SoC contains a Synopsys DesignWare HDMI
> > > > controller
> > > > (paired
> > > > with DesignWare HDMI TX PHY Gen2) that takes the "DP" output
> > > > from
> > > > the
> > > > display controller.
> > > > 
> > > > Add a driver for this controller utilizing the common
> > > > DesignWare
> > > > HDMI
> > > > code in the kernel.
> > > > 
> > > > Signed-off-by: Icenowy Zheng <uwu@icenowy.me>
> > > > Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn>
> > > > ---
> > > > No changes in v3, v4.
> > > > 
> > > > Changes in v2:
> > > > - Created a new function to set PHY parameters and refactored
> > > > the
> > > >  control flow of the configure_phy callback.
> > > > 
> > > > MAINTAINERS                             |   1 +
> > > > drivers/gpu/drm/bridge/Kconfig          |  10 ++
> > > > drivers/gpu/drm/bridge/Makefile         |   1 +
> > > > drivers/gpu/drm/bridge/th1520-dw-hdmi.c | 173
> > > > ++++++++++++++++++++++++
> > > > 4 files changed, 185 insertions(+)
> > > > create mode 100644 drivers/gpu/drm/bridge/th1520-dw-hdmi.c
> > > 
> > > 
> > > As this is a Synopsys DesignWare based IP, maybe it's better to
> > > put
> > > it under   "drivers/gpu/drm/bridge/synopsys/"
> > > Or just create a dir for thead, I think there will come other
> > > display
> > > related drivers for thead in the future.
> > 
> > It's not proper to place vendor glues to synopsys/ .
> 
> 
> TI has precedents for doing this with Cadence IP, see 
> 
> drivers/gpu/drm/bridge/cadence/cdns-dsi-j721e.c
> drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-j721e.c 

Well for this kind of things, I prefer to hear from the maintainer of
DW HDMI bridges (although it seems that this has no dedicated
MAINTAINERS entry and get_maintainers just returns people for DRM
DRIVERS FOR BRIDGE CHIPS).

> 
> 
> > 
> > As for T-Head, they stopped their embedded SoC business (sold to
> > another company) and now they only makes data-center chips, there
> > should be no T-Head display drivers in the future.
> > 
> > > 
> > > 
> > =========== 8< ============
> > 
> > 
> > _______________________________________________
> > linux-riscv mailing list
> > linux-riscv@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-riscv


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

  reply	other threads:[~2025-12-27  7:23 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 [this message]
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   ` [PATCH v4 0/9] Verisilicon DC8200 driver (and adaption to TH1520) Michal Wilczynski

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=3b5fd30554f91bcd083b2dc450cdf7fe2fa395e2.camel@iscas.ac.cn \
    --to=zhengxingda@iscas.ac.cn \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andyshrk@163.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=m.wilczynski@samsung.com \
    --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=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