From: Tim Surber <me@timsurber.de>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
heiko@sntech.de, mchehab@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, p.zabel@pengutronix.de,
jose.abreu@synopsys.com, nelson.costa@synopsys.com,
shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
hverkuil@xs4all.nl, hverkuil-cisco@xs4all.nl
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller
Date: Thu, 9 Jan 2025 00:17:32 +0100 [thread overview]
Message-ID: <d61e344f-fcdd-47af-a142-e8d42edec045@timsurber.de> (raw)
In-Reply-To: <a5226fac-2a5b-47f3-b32e-8662bf932bd4@collabora.com>
Hi,
I tested your patch with the command
# gst-launch-1.0 -v v4l2src device=/dev/video1 ! fakesink
If this worked I moved on to a visual test using
# gst-launch-1.0 -v v4l2src device=/dev/video1 ! queue ! v4l2convert !
waylandsink
I used a Windows PC with a Nvidia GTX 4060 as my source for the
following tests.
| Format | Result |
| ------------ | ------------------------------------------- |
| 4k60p RGB | Recognized as 1080p / 120 fps - no output |
| 4k60p 4:2:2 | Recognized as 1080p / 120 fps - no output |
| 4k60p 4:4:4 | Error: Device wants 1 planes |
| 4k30p RGB | ok |
| 4k30p 4:2:2 | ok |
| 4k30p 4:4:4 | Error: Device wants 1 planes |
| FHD60p RGB | ok |
| FHD60p 4:2:2 | ok |
| FHD60p 4:4:4 | Error: Device wants 1 planes |
When testing 4:4:4 chroma I got the following error:
# gst-launch-1.0 -v v4l2src device=/dev/video1 ! fakesink
/sys/v4l2/gstv4l2object.c(4344): gst_v4l2_object_set_format_full ():
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
Device wants 1 planes
I could record and convert (with errors) the files with 4:4:4 chroma
using the command Shreeya posted, but the resulting video had wrong
colors and was flashing.
I was not able to test 4:2:0 chroma. I tried to generate an custom EDID
with support for it but I could not select it in the graphics driver in
the source, maybe this is just an issue with my setup.
I also observed that the the framerate is reported wrong, for example
setting the source to FHD60p RGB resulted in the following:
# v4l2-ctl --all -L --list-formats-ext -d /dev/video0
Active width: 1920
Active height: 1080
Total width: 2200
Total height: 1125
Frame format: progressive
Polarities: -vsync -hsync
Pixelclock: 214076000 Hz (86.50 frames per second)
This wrong framerate reporting seemed to happen across all framerates
and resolutions. Gstreamer Pipeline negotation showed the same results.
During my testing I got sometimes an error
# dmesg
dma alloc of size 24883200 failed
I'm not sure when this happened and how to reproduce it.
Then I tried to use an AppleTV 4k as source. I don't know what
resolution it tried to negotiate but I got this error in addition to the
previous "Device wants 1 planes" and no connection:
# dmesg
fdee0000.hdmi_receiver: hdmirx_query_dv_timings: signal is not locked
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: signal not lock,
tmds_clk_ratio:0
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: mu_st:0x0, scdc_st:0x0,
dma_st10:0x10
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: signal not lock,
tmds_clk_ratio:0
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: mu_st:0x0, scdc_st:0x0,
dma_st10:0x14
Best regards,
Tim
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-01-08 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:39 [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 1/4] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 2/4] dt-bindings: media: Document bindings for HDMI RX Controller Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 3/4] arm64: dts: rockchip: Add device tree support " Shreeya Patel
2024-12-10 19:39 ` [RESEND PATCH v5 4/4] media: platform: synopsys: Add support for HDMI input driver Shreeya Patel
2025-02-10 13:46 ` Hans Verkuil
2025-02-11 16:02 ` Dmitry Osipenko
2025-01-06 0:26 ` [RESEND PATCH v5 0/4] Add Synopsys DesignWare HDMI RX Controller Tim Surber
[not found] ` <acb91a34-c0f8-4f03-8945-755b4e42dcf3@timsurber.de>
2025-01-06 11:22 ` Dmitry Osipenko
2025-01-07 0:08 ` Tim Surber
2025-01-07 7:27 ` Dmitry Osipenko
2025-01-08 23:17 ` Tim Surber [this message]
2025-01-14 11:37 ` Dmitry Osipenko
2025-01-14 14:16 ` Nicolas Dufresne
2025-01-19 2:14 ` Tim Surber
2025-01-23 11:21 ` 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=d61e344f-fcdd-47af-a142-e8d42edec045@timsurber.de \
--to=me@timsurber.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=heiko@sntech.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=jose.abreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=nelson.costa@synopsys.com \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--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