From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, Tim Surber <me@timsurber.de>,
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,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Diederik de Haas <didi.debian@cknow.org>
Subject: Re: [PATCH v13 0/6] Add Synopsys DesignWare HDMI RX Controller
Date: Wed, 5 Mar 2025 12:09:46 +0300 [thread overview]
Message-ID: <47e022f4-1c1b-43c4-8f6c-bc1ff23ad39f@collabora.com> (raw)
In-Reply-To: <88054acf-3051-414c-aef7-4c0f085d5182@collabora.com>
On 3/5/25 12:03, Dmitry Osipenko wrote:
> On 3/5/25 11:10, Hans Verkuil wrote:
>> On 05/03/2025 01:59, Tim Surber wrote:
>>> Hi Dmitry,
>>>
>>> I did some more testing. That the Apple TV did not work was a bit
>>> misleading.
>>>
>>> It was just, that the Apple TV defaulted to 4:4:4 Chroma which does not
>>> work at all for me. (The same happens using the vendor driver).
>>>
>>> When I changed the EDID to match the vendor driver the HDMI handshake
>>> happened with 4:2:0 chroma, where I could verify even 4k60fps using your
>>> driver, nice!
>>>
>>> So the remaining problems I see are:
>>> - 4:4:4 chroma not working in any resolution
>>> - 4:2:2 and RGB not working in 4k60fps (is this a hardware limitation?)
>>>
>>> A possible workaround could be to disable these non supported formats in
>>> the default EDID.
>> I would like to merge this driver this week, since otherwise it will likely
>> slip to v6.16. So if there is a working EDID, perhaps it can be used for now,
>> and later on it can be patched if there is a better EDID.
>>
>> Would this EDID work? Tim, can you try this?
>>
>> v4l2-ctl --set-edid type=hdmi-4k-600mhz,ycbcr444,ycbcr422
>>
>> Alternatively, if there is indeed a HW limitation that prevents 4kp60 to work,
>> try this:
>>
>> v4l2-ctl --set-edid type=hdmi-4k-300mhz,ycbcr444,ycbcr422
>>
>> Whichever of the two works is what we can use as default EDID.
>
> Disabling 444 and 422 is an option. Though, they work on my setup at
> 4k@60p.
>
> In general, it often a challenge to get 4k@60p properly with any of
> these small board devices. 4k@60p works only using a short HDMI cable
> for me. Also, not everyone aware that the micro HDMI adapter needs to be
> compliant with HDMI 2.0 for 4k@60, that's why 300MHz is the default.
>
> Will be nice to have the good EDID enabled by default in the defconfig.
> Dealing with problems like that will be a headache for majority of
> people, IMO.
BTW, I don't see it as a blocker. Driver works in general, new issues
can be resolved with additional patches.
--
Best regards,
Dmitry
next prev parent reply other threads:[~2025-03-05 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 8:58 [PATCH v13 0/6] Add Synopsys DesignWare HDMI RX Controller Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 1/6] MAINTAINERS: Add entry for Synopsys DesignWare HDMI RX Driver Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 2/6] dt-bindings: media: Document bindings for HDMI RX Controller Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 3/6] media: platform: synopsys: Add support for HDMI input driver Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 4/6] arm64: dts: rockchip: Add device tree support for HDMI RX Controller Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 5/6] arm64: dts: rockchip: Enable HDMI receiver on rock-5b Dmitry Osipenko
2025-03-04 8:58 ` [PATCH v13 6/6] arm64: defconfig: Enable Synopsys HDMI receiver Dmitry Osipenko
2025-03-04 16:43 ` [PATCH v13 0/6] Add Synopsys DesignWare HDMI RX Controller Tim Surber
2025-03-04 17:17 ` Hans Verkuil
2025-03-05 0:59 ` Tim Surber
2025-03-05 8:10 ` Hans Verkuil
2025-03-05 9:03 ` Dmitry Osipenko
2025-03-05 9:09 ` Dmitry Osipenko [this message]
2025-03-05 10:41 ` Tim Surber
2025-03-05 10:53 ` Dmitry Osipenko
2025-04-04 16:25 ` Nicolas Dufresne
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=47e022f4-1c1b-43c4-8f6c-bc1ff23ad39f@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.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