Linux IIO development
 help / color / mirror / Atom feed
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 v2 0/2] iio: light: vcnl4000: support shared IRQs
Date: Mon, 17 Aug 2026 13:55:40 +0300	[thread overview]
Message-ID: <aoLorPM301oeipKz@ashevche-desk.local> (raw)
In-Reply-To: <20260814-vcnl4000-v2-0-9b771290cc1d@jacques.com.au>

On Fri, Aug 14, 2026 at 02:30:41PM +1000, Tsz Shan Chan wrote:
> This series contains two changes for the vcnl4000 driver.
> 
> Patch 1 makes .num_channels match .channels for vcnl4200. vcnl4040 and
> vcnl4000 channel arrays have the same size, so no functional change.
> 
> Patch 2 adds shared IRQ support. It changes the trigger type from
> falling edge to low level and adds IRQF_SHARED. The IRQ handlers return
> IRQ_NONE when the device did not generate the interrupt.

LGTM,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-08-17 10:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  4:30 [PATCH v2 0/2] iio: light: vcnl4000: support shared IRQs Tsz Shan Chan
2026-08-14  4:30 ` [PATCH v2 1/2] iio: light: vcnl4000: use correct channel array size Tsz Shan Chan
2026-08-14  4:30 ` [PATCH v2 2/2] iio: light: vcnl4000: add shared IRQ support Tsz Shan Chan
2026-08-22  2:25   ` Jonathan Cameron
2026-08-24  8:24     ` Andy Shevchenko
2026-08-25  3:22       ` Tsz Shan Chan
2026-08-25  8:48         ` Andy Shevchenko
2026-08-28  8:09           ` Tsz Shan Chan
2026-08-17 10:55 ` Andy Shevchenko [this message]
2026-08-22  2:29   ` [PATCH v2 0/2] iio: light: vcnl4000: support shared IRQs Jonathan Cameron
2026-08-28  8:13     ` Tsz Shan Chan

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=aoLorPM301oeipKz@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