public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Vladimir Yakovlev" <vovchkir@gmail.com>
Cc: <Laurent.pinchart@ideasonboard.com>, <airlied@gmail.com>,
	<andrzej.hajda@intel.com>, <dmitry.baryshkov@oss.qualcomm.com>,
	<dri-devel@lists.freedesktop.org>, <jernej.skrabec@gmail.com>,
	<jonas@kwiboo.se>, <linux-kernel@vger.kernel.org>,
	<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
	<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
	<simona@ffwll.ch>, <tzimmermann@suse.de>
Subject: Re: [PATCH v2 1/1] drm/bridge: lontium-lt9611uxc: use irq as optional parameter
Date: Wed, 07 Jan 2026 10:23:01 +0100	[thread overview]
Message-ID: <DFI8X9FKRV12.1XNFGJDUWR5PR@bootlin.com> (raw)
In-Reply-To: <20260107032342.332758-2-vovchkir@gmail.com>

On Wed Jan 7, 2026 at 4:23 AM CET, Vladimir Yakovlev wrote:
> On some systems the interrupt pin may not be used.
> In this case we exclude DRM_BRIDGE_OP_HPD from supported operations,
> after which a polling thread is started to detect the connection.
> (the default polling period for DRM is 10 seconds)
>
> Signed-off-by: Vladimir Yakovlev <vovchkir@gmail.com>
> ---
>  drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 20 +++++++++++++-------
>  1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/lontium-lt9611uxc.c b/drivers/gpu/drm/bridge/lontium-lt9611uxc.c
> index bb5cff021c93..f7a74ec1f170 100644
> --- a/drivers/gpu/drm/bridge/lontium-lt9611uxc.c
> +++ b/drivers/gpu/drm/bridge/lontium-lt9611uxc.c
> @@ -851,19 +851,25 @@ static int lt9611uxc_probe(struct i2c_client *client)
>  	init_waitqueue_head(&lt9611uxc->wq);
>  	INIT_WORK(&lt9611uxc->work, lt9611uxc_hpd_work);
>
> -	ret = devm_request_threaded_irq(dev, client->irq, NULL,
> -					lt9611uxc_irq_thread_handler,
> -					IRQF_ONESHOT, "lt9611uxc", lt9611uxc);
> -	if (ret) {
> -		dev_err(dev, "failed to request irq\n");
> -		goto err_disable_regulators;
> +	if (client->irq) {
> +		ret = devm_request_threaded_irq(dev, client->irq, NULL,
> +						lt9611uxc_irq_thread_handler,
> +						IRQF_ONESHOT, "lt9611uxc", lt9611uxc);
> +		if (ret) {
> +			dev_err(dev, "failed to request irq\n");
> +			goto err_disable_regulators;
> +		}
> +		dev_dbg(dev, "Uses IRQ\n");
> +	} else {
> +		dev_dbg(dev, "The interrupt (IRQ) is not specified in the DTS.\n");
> +		dev_dbg(dev, "Check the interrupt (IRQ) or polling will be used!!!\n");
>  	}

Thanks for having moved form a warning to a dbg. However these 2 lines are
overly verbose and that's not really needed. I would prefer to see all
those 3 dev_dbg() disappear honestly, being polling a perfectly supported
use case here. But if you really really want to keep them, at least replace
these 2 lines with just a "Uses polling\n" which gives the same info. Also
the 2 consecutive dev_dbg() may mix with other logging, making it awkward
to read in the logs.

Luca

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-01-07  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07  3:23 [PATCH v2 0/1] drm/bridge: lontium-lt9611uxc: use irq as optional Vladimir Yakovlev
2026-01-07  3:23 ` [PATCH v2 1/1] drm/bridge: lontium-lt9611uxc: use irq as optional parameter Vladimir Yakovlev
2026-01-07  9:23   ` Luca Ceresoli [this message]
2026-01-07  9:09 ` [PATCH v2 0/1] drm/bridge: lontium-lt9611uxc: use irq as optional Luca Ceresoli

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=DFI8X9FKRV12.1XNFGJDUWR5PR@bootlin.com \
    --to=luca.ceresoli@bootlin.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rfoss@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=vovchkir@gmail.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