From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
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, nicolas.dufresne@collabora.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>
Subject: Re: [PATCH v6 4/6] media: platform: synopsys: Add support for HDMI input driver
Date: Mon, 17 Feb 2025 18:36:56 +0300 [thread overview]
Message-ID: <3d4b1c45-cc00-4714-8582-0848e38c2ec4@collabora.com> (raw)
In-Reply-To: <110db742-25a0-4f0c-9620-1af8885d6e1c@xs4all.nl>
On 2/17/25 11:31, Hans Verkuil wrote:
> On 15/02/2025 22:04, Dmitry Osipenko wrote:
>> From: Shreeya Patel <shreeya.patel@collabora.com>
>>
>> Add initial support for the Synopsys DesignWare HDMI RX
>> Controller Driver used by Rockchip RK3588. The driver
>> supports:
>> - HDMI 1.4b and 2.0 modes (HDMI 4k@60Hz)
>> - RGB888, YUV422, YUV444 and YCC420 pixel formats
>> - CEC
>> - EDID configuration
>>
>> The hardware also has Audio and HDCP capabilities, but these are
>> not yet supported by the driver.
>>
>> Co-developed-by: Dingxian Wen <shawn.wen@rock-chips.com>
>> Signed-off-by: Dingxian Wen <shawn.wen@rock-chips.com>
>> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
>> Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>> ---
>> drivers/media/platform/Kconfig | 1 +
>> drivers/media/platform/Makefile | 1 +
>> drivers/media/platform/synopsys/Kconfig | 3 +
>> drivers/media/platform/synopsys/Makefile | 2 +
>> .../media/platform/synopsys/hdmirx/Kconfig | 27 +
>> .../media/platform/synopsys/hdmirx/Makefile | 4 +
>> .../platform/synopsys/hdmirx/snps_hdmirx.c | 2715 +++++++++++++++++
>> .../platform/synopsys/hdmirx/snps_hdmirx.h | 394 +++
>> .../synopsys/hdmirx/snps_hdmirx_cec.c | 284 ++
>> .../synopsys/hdmirx/snps_hdmirx_cec.h | 44 +
>> 10 files changed, 3475 insertions(+)
>> create mode 100644 drivers/media/platform/synopsys/Kconfig
>> create mode 100644 drivers/media/platform/synopsys/Makefile
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/Kconfig
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/Makefile
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/snps_hdmirx.h
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/snps_hdmirx_cec.c
>> create mode 100644 drivers/media/platform/synopsys/hdmirx/snps_hdmirx_cec.h
>>
>
> <snip>
>
>> +static ssize_t
>> +hdmirx_debugfs_if_read(u32 type, void *priv, struct file *filp,
>> + char __user *ubuf, size_t count, loff_t *ppos)
>> +{
>> + struct snps_hdmirx_dev *hdmirx_dev = priv;
>> + u8 aviif[3 + 7 * 4];
>> + int len;
>> +
>> + if (type != V4L2_DEBUGFS_IF_AVI)
>> + return 0;
>> +
>> + hdmirx_read_avi_infoframe(hdmirx_dev, aviif);
>> +
>> + len = simple_read_from_buffer(ubuf, count, ppos,
>> + aviif, ARRAY_SIZE(aviif));
>> +
>> + return len < 0 ? 0 : len;
>> +}
>
> Have you tested this with 'edid-decode -c -I /path/to/avi'? Also test that it is
> empty if there is no AVI InfoFrame (e.g. when there is no incoming video). I don't see
> a test for that in the code.
>
> I also see no sanity check regarding the length of the InfoFrame, it just outputs
> the full array, meaning you get padding as well since the AVI InfoFrame is smaller
> than ARRAY_SIZE(aviif). In fact, edid-decode will fail about that if the -c option
> is used.
>
> See tc358743_debugfs_if_read of how this is typically handled.
I've tested with 'edid-decode -I /path/to/avi', including the empty AVI
InfoFrame. But without the '-c option'. I'd expect that debugfs should
provide a full-sized raw InfoFrame data, rather than a parsed version.
The parsed data isn't much useful for debugging purposes, IMO. I
intentionally removed the size check that tc358743_debugfs_if_read does
because it appeared wrong to me. Will re-check with '-c option', thanks!
--
Best regards,
Dmitry
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-17 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 21:04 [PATCH v6 0/6] Add Synopsys DesignWare HDMI RX Controller Dmitry Osipenko
2025-02-15 21:04 ` [PATCH v6 1/6] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Dmitry Osipenko
2025-02-15 21:04 ` [PATCH v6 2/6] dt-bindings: media: Document bindings for HDMI RX Controller Dmitry Osipenko
2025-02-15 21:04 ` [PATCH v6 3/6] arm64: dts: rockchip: Add device tree support " Dmitry Osipenko
2025-02-15 21:04 ` [PATCH v6 4/6] media: platform: synopsys: Add support for HDMI input driver Dmitry Osipenko
2025-02-17 8:31 ` Hans Verkuil
2025-02-17 15:36 ` Dmitry Osipenko [this message]
2025-02-17 15:44 ` Hans Verkuil
2025-02-17 18:21 ` Dmitry Osipenko
2025-02-17 18:26 ` Dmitry Osipenko
2025-02-17 18:45 ` Hans Verkuil
2025-02-15 21:04 ` [PATCH v6 5/6] arm64: defconfig: Enable Synopsys HDMI receiver Dmitry Osipenko
2025-02-15 21:04 ` [PATCH v6 6/6] arm64: dts: rockchip: Enable HDMI receiver on rock-5b Dmitry Osipenko
2025-02-17 8:34 ` [PATCH v6 0/6] Add Synopsys DesignWare HDMI RX Controller Hans Verkuil
2025-02-17 18:16 ` 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=3d4b1c45-cc00-4714-8582-0848e38c2ec4@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=nicolas.dufresne@collabora.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