From: Heiko Stuebner <heiko@sntech.de>
To: dmitry.baryshkov@oss.qualcomm.com, Andy Yan <andyshrk@163.com>,
neil.armstrong@linaro.org, andrzej.hajda@intel.com
Cc: mripard@kernel.org, jernej.skrabec@gmail.com, jonas@kwiboo.se,
Laurent.pinchart@ideasonboard.com,
maarten.lankhorst@linux.intel.com, rfoss@kernel.org,
simona@ffwll.ch, tzimmermann@suse.de, knaerzche@gmail.com,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v8 1/2] drm/rockchip: inno-hdmi: Convert to drm bridge
Date: Mon, 20 Oct 2025 14:45:34 +0200 [thread overview]
Message-ID: <8913609.MhkbZ0Pkbq@phil> (raw)
In-Reply-To: <20251016083843.76675-2-andyshrk@163.com>
Am Donnerstag, 16. Oktober 2025, 10:38:31 Mitteleuropäische Sommerzeit schrieb Andy Yan:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> Convert it to drm bridge driver, it will be convenient for us to
> migrate the connector part to the display driver later.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
But of course I would be really happy if someone with more experience
on general bridges could also take a look.
Heiko
next prev parent reply other threads:[~2025-10-20 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 8:38 [PATCH v8 0/2] Convert inno hdmi to drm bridge Andy Yan
2025-10-16 8:38 ` [PATCH v8 1/2] drm/rockchip: inno-hdmi: Convert " Andy Yan
2025-10-20 12:45 ` Heiko Stuebner [this message]
2025-11-24 0:52 ` Andy Yan
2025-12-24 22:28 ` Dmitry Baryshkov
2025-10-16 8:38 ` [PATCH v8 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library Andy Yan
2025-10-17 7:58 ` Maud Spierings
2025-10-17 8:56 ` Andy Yan
2025-10-17 9:19 ` Maud Spierings
2025-10-17 9:36 ` Andy Yan
2025-12-24 22:29 ` Dmitry Baryshkov
2025-12-24 22:32 ` [PATCH v8 0/2] Convert inno hdmi to drm bridge Dmitry Baryshkov
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=8913609.MhkbZ0Pkbq@phil \
--to=heiko@sntech.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@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;
as well as URLs for NNTP newsgroup(s).