From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
jose.abreu@synopsys.com, nelson.costa@synopsys.com,
shawn.wen@rock-chips.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, Tim Surber <me@timsurber.de>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: Re: [PATCH v10 6/6] arm64: defconfig: Enable Synopsys HDMI receiver
Date: Thu, 27 Feb 2025 22:51:37 -0500 [thread overview]
Message-ID: <863f9c1beb7a912f94f8740b3e5095e09e49cee5.camel@collabora.com> (raw)
In-Reply-To: <a8a6c8c8-ee3b-422a-8573-a2cbb61fc3aa@xs4all.nl>
Hi Hans,
Le mercredi 26 février 2025 à 09:31 +0100, Hans Verkuil a écrit :
> On 25/02/2025 19:30, Dmitry Osipenko wrote:
> > From: Sebastian Reichel <sebastian.reichel@collabora.com>
> >
> > The Rockchip RK3588 has a built-in HDMI receiver block from
> > Synopsys. Let's enable the driver for it.
> >
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> > Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > ---
> > arch/arm64/configs/defconfig | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/arm64/configs/defconfig
> > b/arch/arm64/configs/defconfig
> > index cb7da4415599..3dccc9e1c4aa 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -859,6 +859,8 @@ CONFIG_VIDEO_SAMSUNG_EXYNOS_GSC=m
> > CONFIG_VIDEO_SAMSUNG_S5P_JPEG=m
> > CONFIG_VIDEO_SAMSUNG_S5P_MFC=m
> > CONFIG_VIDEO_SUN6I_CSI=m
> > +CONFIG_VIDEO_SYNOPSYS_HDMIRX=m
> > +CONFIG_VIDEO_SYNOPSYS_HDMIRX_LOAD_DEFAULT_EDID=y
>
> I do not believe it is a good idea to default to y for this option.
>
> The EDID depends on the specific device you make, and you should
> think carefully about whether the default EDID fits the needs of the
> device.
>
> So if you want the default EDID, then you should manually select it
> and not have it autoselected.
Following up here, from the device maker perspective sure, but I'm not
sure this is the best choice for generic Linux distribution. As of
today, pretty much no userspace capture software knows about this,
meaning the device will not work out of the box in OBS, GStreamer,
Ffmpeg, Web Browsers. In comparison, if you pick any UVC HDMI capture,
it just work, with a default EDID that covers the range of
capabilities, which in this case are defined by the SoC.
Whatever we make as a choice, will always be the wrong choice for
someone, though I expect this to be a lot easier to change for
"specialized" implementation. Now, since there is no reason you can't
do a specilized implementation on generic Linux distro, and because you
might disagree with me, perhaps a compromise is to also add a module
parameter, so that there is a run-time override to this.
Nicolas
>
> Regards,
>
> Hans
>
> > CONFIG_VIDEO_TI_J721E_CSI2RX=m
> > CONFIG_VIDEO_HANTRO=m
> > CONFIG_VIDEO_IMX219=m
>
>
--
Nicolas Dufresne
Principal Engineer at Collabora
next prev parent reply other threads:[~2025-02-28 3:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 18:30 [PATCH v10 0/6] Add Synopsys DesignWare HDMI RX Controller Dmitry Osipenko
2025-02-25 18:30 ` [PATCH v10 1/6] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Dmitry Osipenko
2025-02-26 8:44 ` Krzysztof Kozlowski
2025-02-26 9:24 ` Dmitry Osipenko
2025-02-25 18:30 ` [PATCH v10 2/6] dt-bindings: media: Document bindings for HDMI RX Controller Dmitry Osipenko
2025-02-25 18:30 ` [PATCH v10 3/6] media: platform: synopsys: Add support for HDMI input driver Dmitry Osipenko
2025-02-26 8:47 ` Hans Verkuil
2025-02-26 9:24 ` Dmitry Osipenko
2025-02-26 15:14 ` Diederik de Haas
2025-02-27 5:28 ` Dmitry Osipenko
2025-02-27 11:16 ` Diederik de Haas
2025-02-27 19:40 ` Nicolas Dufresne
2025-02-25 18:30 ` [PATCH v10 4/6] arm64: dts: rockchip: Add device tree support for HDMI RX Controller Dmitry Osipenko
2025-02-25 18:30 ` [PATCH v10 5/6] arm64: dts: rockchip: Enable HDMI receiver on rock-5b Dmitry Osipenko
2025-02-25 18:30 ` [PATCH v10 6/6] arm64: defconfig: Enable Synopsys HDMI receiver Dmitry Osipenko
2025-02-26 8:31 ` Hans Verkuil
2025-02-26 9:24 ` Dmitry Osipenko
2025-02-28 3:51 ` Nicolas Dufresne [this message]
2025-03-04 16:17 ` Hans Verkuil
2025-03-05 11:08 ` Dmitry Osipenko
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=863f9c1beb7a912f94f8740b3e5095e09e49cee5.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jose.abreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=me@timsurber.de \
--cc=nelson.costa@synopsys.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.wen@rock-chips.com \
--cc=shreeya.patel@collabora.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