From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shreeya Patel <shreeya.patel@collabora.com>,
Hans Verkuil <hverkuil@kernel.org>,
Dingxian Wen <shawn.wen@rock-chips.com>
Cc: linux-media@vger.kernel.org, kernel@collabora.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] media: synopsys: hdmirx: stop logging a missing signal at error level
Date: Tue, 22 Sep 2026 15:54:16 +0300 [thread overview]
Message-ID: <b636eebe-552c-404d-8cea-3ae2d29ce4b8@collabora.com> (raw)
In-Reply-To: <20260921-hdmirx-fixes-v1-3-495be0beaf93@pengutronix.de>
On 9/21/26 10:15, Sascha Hauer wrote:
> hdmirx_query_dv_timings() refuses with -ENOLINK while the source is not
> driving the connector's +5V line and with -ENOLCK while the receiver has
> not locked, and prints both at v4l2_err level. Neither is a driver error.
> They are the two states a receiver sits in whenever nothing is plugged
> in, and the way userspace waits for a source is to poll until they clear,
> so an application doing the expected thing fills the kernel log.
>
> Both states are now reported through VIDIOC_ENUMINPUT as
> V4L2_IN_ST_NO_POWER and V4L2_IN_ST_NO_SIGNAL, from the same two helpers,
> so the prints no longer carry anything userspace cannot ask for. Drop
> them to v4l2_dbg level 1, where the other non-error outcome of this
> function, timings out of range, already is.
>
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> index 75576a9366fd0..41f6112ec8123 100644
> --- a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> +++ b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> @@ -502,12 +502,12 @@ static int hdmirx_query_dv_timings(struct file *file, void *priv,
> int ret;
>
> if (port_no_link(hdmirx_dev)) {
> - v4l2_err(v4l2_dev, "%s: port has no link\n", __func__);
> + v4l2_dbg(1, debug, v4l2_dev, "%s: port has no link\n", __func__);
> return -ENOLINK;
> }
>
> if (signal_not_lock(hdmirx_dev)) {
> - v4l2_err(v4l2_dev, "%s: signal is not locked\n", __func__);
> + v4l2_dbg(1, debug, v4l2_dev, "%s: signal is not locked\n", __func__);
> return -ENOLCK;
> }
>
>
Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
--
Best regards,
Dmitry
prev parent reply other threads:[~2026-09-22 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:15 [PATCH 0/3] media: synopsys: hdmirx: pixelclock fix and input status reporting Sascha Hauer
2026-09-21 7:15 ` [PATCH 1/3] media: synopsys: hdmirx: fetch colordepth before calculating pixelclock Sascha Hauer
2026-09-22 12:50 ` Dmitry Osipenko
2026-09-21 7:15 ` [PATCH 2/3] media: synopsys: hdmirx: add input status reporting to VIDIOC_ENUMINPUT Sascha Hauer
2026-09-22 12:53 ` Dmitry Osipenko
2026-09-21 7:15 ` [PATCH 3/3] media: synopsys: hdmirx: stop logging a missing signal at error level Sascha Hauer
2026-09-22 12:54 ` Dmitry Osipenko [this message]
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=b636eebe-552c-404d-8cea-3ae2d29ce4b8@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=hverkuil@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®