All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>,
	Dmitry Osipenko <dmitry.osipenko@collabora.com>,
	Shreeya Patel <shreeya.patel@collabora.com>
Cc: linux-media@vger.kernel.org, kernel@collabora.com
Subject: Re: "signal is not locked" with HDMI RX driver on RK3588
Date: Mon, 30 Jun 2025 15:57:03 +0200	[thread overview]
Message-ID: <aGKXr0Z96zGU74q6@mail-itl> (raw)
In-Reply-To: <aGKFhDmBwYp5KV3k@mail-itl>

[-- Attachment #1: Type: text/plain, Size: 2476 bytes --]

On Mon, Jun 30, 2025 at 02:39:32PM +0200, Marek Marczykowski-Górecki wrote:
> Hi,
> 
> First of all, thanks for all the work regarding upstreaming the driver!
> 
> I try to use it on two boards:
> - Orange Pi 5B
> - Rock 5B+
> 
> In both cases, when I use the upstream driver in 6.16-rc, I hit similar
> issue:
> 1. `v4l2-ctl -d /dev/video2 --set-edid type=hdmi-4k-300mhz` - this works
> 2. EDID is properly presented to the device on the other side of the
> HDMI cable, I can select to use that "display"
> 3. But then, the hdmirx complains:
> 
>     v4l2-ctl -d /dev/video2 --query-dv-timings
>     VIDIOC_QUERY_DV_TIMINGS: failed: No locks available
> 
> And kernel shows:
> [ 4033.823023] snps_hdmirx fdee0000.hdmi_receiver: hdmirx_phy_register_write wait cr write done failed
> [ 4033.847027] snps_hdmirx fdee0000.hdmi_receiver: hdmirx_phy_register_write wait cr write done failed
> [ 4033.870976] snps_hdmirx fdee0000.hdmi_receiver: hdmirx_phy_register_write wait cr write done failed
> [ 4033.894998] snps_hdmirx fdee0000.hdmi_receiver: hdmirx_phy_register_write wait cr write done failed
> ...
> [ 4061.975400] fdee0000.hdmi_receiver: hdmirx_query_dv_timings: signal is not locked
> 
> In this state actually capturing video stream doesn't work either.
> 
> I tried also rockchip-release branch from
> https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux (at
> 33755850faeb0e53e634390d147cc261a60d2898) with the same result.
> 
> If I try the same with the 6.12.13-current-rockchip64 kernel from Armbian,
> it works fine. I tried to compare the drivers, but there are quite a few
> differences so it's hard to spot any obvious issue (it could be also an
> issue somewhere else...).
> 
> Any ideas? I can try to add some debugging info or test patches, if you
> point me what would be helpful.

If I take u-boot from
https://gitlab.collabora.com/hardware-enablement/rockchip-3588/u-boot/
(rockchip branch at 60501605e3f48b155af83193dfd9ad73362b8e25) and stop
loading device-tree from a separate file, I get a different error:

    VIDIOC_QUERY_DV_TIMINGS: failed: Numerical result out of range

(and no extra messages from kernel)
My goal is to capture in 4k at 30fps (or even lower), but I get this
error also with lower resolutions like 1920x1200@60fps. Unfortunately I
don't know which value specifically is out of range...

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-06-30 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 12:39 "signal is not locked" with HDMI RX driver on RK3588 Marek Marczykowski-Górecki
2025-06-30 13:57 ` Marek Marczykowski-Górecki [this message]
2025-06-30 17:51   ` Sebastian Reichel
2025-07-01 23:20     ` Marek Marczykowski-Górecki
2025-07-02 16:23       ` 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=aGKXr0Z96zGU74q6@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=dmitry.osipenko@collabora.com \
    --cc=kernel@collabora.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sebastian.reichel@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.