From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Tsz Shan Chan <tsz.chan.dev@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Tsz Shan Chan" <tchan@jacques.com.au>
Subject: Re: [PATCH v3 4/5] iio: light: vcnl4000: Add IRQ disable callback on cleanup
Date: Thu, 3 Sep 2026 11:03:33 +0300 [thread overview]
Message-ID: <apkp1SdLzs_zZ6jB@ashevche-desk.local> (raw)
In-Reply-To: <20260903-vcnl4000-v3-4-5e69c2e715a8@jacques.com.au>
On Thu, Sep 03, 2026 at 02:53:49PM +1000, Tsz Shan Chan wrote:
> During driver unbind, devm cleans up resources in LIFO order. The IRQ
> handler is freed before the device is powered down. This can lead to
> unhandled interrupts.
>
> Register a devm action to disable interrupt explicitly after
> devm_request_threaded_irq(), so that the interrupt is disabled before
> the IRQ handler is freed. This prevents any unhandled interrupts.
>
> Add a disable_irq callback to chip info structure. This allows each chip
> type to implement its own disable sequence.
...
> +static int vcnl4010_disable_irq(struct vcnl4000_data *data)
> +{
> + int ret;
> +
> + guard(mutex)(&data->vcnl4000_lock);
> +
> + ret = vcnl4010_stop(data);
> + if (ret < 0)
> + return ret;
> +
> + ret = i2c_smbus_read_byte_data(data->client, VCNL4010_ISR);
> + if (ret < 0)
> + return ret;
> + ret &= VCNL4010_INT_THR | VCNL4010_INT_DRDY;
> + if (!ret)
> + return 0;
> +
> + return i2c_smbus_write_byte_data(data->client, VCNL4010_ISR, ret);
Since ret is in use it's better to follow regular pattern
ret &= VCNL4010_INT_THR | VCNL4010_INT_DRDY;
if (ret)
return i2c_smbus_write_byte_data(data->client, VCNL4010_ISR, ret);
return 0;
BUT, since ret doesn't care an error code at this point, it's even better to
use proper typing.
u8 byte;
...
byte = ret & (VCNL4010_INT_THR | VCNL4010_INT_DRDY);
if (!byte)
return 0;
return i2c_smbus_write_byte_data(data->client, VCNL4010_ISR, byte);
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-03 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 4:53 [PATCH v3 0/5] iio: light: vcnl4000: support shared IRQs Tsz Shan Chan
2026-09-03 4:53 ` [PATCH v3 1/5] iio: light: vcnl4000: use correct channel array size Tsz Shan Chan
2026-09-03 7:55 ` Andy Shevchenko
2026-09-03 4:53 ` [PATCH v3 2/5] iio: light: vcnl4000: clear DRDY interrupt when buffer disabled Tsz Shan Chan
2026-09-03 7:55 ` Andy Shevchenko
2026-09-06 18:18 ` Jonathan Cameron
2026-09-03 4:53 ` [PATCH v3 3/5] iio: light: vcnl4000: refactor interrupt config functions Tsz Shan Chan
2026-09-03 4:53 ` [PATCH v3 4/5] iio: light: vcnl4000: Add IRQ disable callback on cleanup Tsz Shan Chan
2026-09-03 8:03 ` Andy Shevchenko [this message]
2026-09-06 18:41 ` Jonathan Cameron
2026-09-03 4:53 ` [PATCH v3 5/5] iio: light: vcnl4000: add shared IRQ support Tsz Shan Chan
2026-09-03 8:07 ` Andy Shevchenko
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=apkp1SdLzs_zZ6jB@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=tchan@jacques.com.au \
--cc=tsz.chan.dev@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