From: Jonathan Cameron <jic23@kernel.org>
To: Esben Haabendal <esben@geanix.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Nikita Travkin" <nikita@trvn.ru>,
"Maslov Dmitry" <maslovdmitry@seeed.cc>,
"Kuppuswamy Sathyanarayanan"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Pan Chuang" <panchuang@vivo.com>,
"Yangtao Li" <frank.li@vivo.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"Andy Shevchenko" <andriy.shevchenko@intel.com>
Subject: Re: [PATCH v5 4/8] iio: light: ltr501: Power down chip if request irq fails
Date: Sun, 23 Aug 2026 00:38:09 +0100 [thread overview]
Message-ID: <20260823003809.25a19c2d@jic23-huawei> (raw)
In-Reply-To: <20260817-liteon-ltr329-v5-4-6f71ab2b0588@geanix.com>
On Mon, 17 Aug 2026 19:08:53 +0200
Esben Haabendal <esben@geanix.com> wrote:
> In case devm_request_threaded_irq() failed, we were leaving the chip
> powered instead of powering it down again. Power down the chip switching
> ALS and PS modes to standby.
>
> Fixes: 7ac702b3144b ("iio: ltr501: Add interrupt support")
> Cc: stable@vger.kernel.org
> Acked-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> Signed-off-by: Esben Haabendal <esben@geanix.com>
> ---
> drivers/iio/light/ltr501.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/light/ltr501.c b/drivers/iio/light/ltr501.c
> index 7d045be78c6d..7746d374688f 100644
> --- a/drivers/iio/light/ltr501.c
> +++ b/drivers/iio/light/ltr501.c
> @@ -1540,7 +1540,7 @@ static int ltr501_probe(struct i2c_client *client)
> if (ret) {
> dev_err(&client->dev, "request irq (%d) failed\n",
> client->irq);
Some noise on this one because the above print is gone in the iio tree.
Anyhow, I think I didn't mess up the conflict resolution but please check!
Next patch also goes away for same reason
Jonathan
> - return ret;
> + goto powerdown_on_error;
> }
> } else {
> indio_dev->info = data->chip_info->info_no_irq;
>
next prev parent reply other threads:[~2026-08-22 23:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 17:08 [PATCH v5 0/8] iio: light: ltr501: Add ltr329 support Esben Haabendal
2026-08-17 17:08 ` [PATCH v5 1/8] dt-bindings: iio: light: ltr501: Sort compatible enum array Esben Haabendal
2026-08-17 17:08 ` [PATCH v5 2/8] dt-bindings: iio: light: ltr501: Add missing ltr303 compatible Esben Haabendal
2026-08-17 17:08 ` [PATCH v5 3/8] dt-bindings: iio: light: ltr501: Add ltr329 compatible Esben Haabendal
2026-08-17 17:08 ` [PATCH v5 4/8] iio: light: ltr501: Power down chip if request irq fails Esben Haabendal
2026-08-17 17:18 ` sashiko-bot
2026-08-22 23:38 ` Jonathan Cameron [this message]
2026-08-17 17:08 ` [PATCH v5 5/8] iio: light: ltr501: Drop duplicated error message Esben Haabendal
2026-08-22 23:39 ` Jonathan Cameron
2026-08-17 17:08 ` [PATCH v5 6/8] iio: light: ltr501: Add ltr329 driver support Esben Haabendal
2026-08-17 17:08 ` [PATCH v5 7/8] iio: light: ltr501: Fix sorting order of device arrays Esben Haabendal
2026-08-17 17:21 ` sashiko-bot
2026-08-17 17:08 ` [PATCH v5 8/8] dt-bindings: iio: light: ltr501: Make proximity-near-level conditional Esben Haabendal
2026-08-21 7:34 ` Krzysztof Kozlowski
2026-08-22 23:40 ` [PATCH v5 0/8] iio: light: ltr501: Add ltr329 support Jonathan Cameron
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=20260823003809.25a19c2d@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=esben@geanix.com \
--cc=frank.li@vivo.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maslovdmitry@seeed.cc \
--cc=nikita@trvn.ru \
--cc=nuno.sa@analog.com \
--cc=panchuang@vivo.com \
--cc=robh@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
/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