Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "Mårten Lindahl" <marten.lindahl@axis.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>, <linux-iio@vger.kernel.org>,
	<kernel@axis.com>
Subject: Re: [PATCH v3 0/3] iio: light: vcnl4000: Add vcnl4040 interrupt support
Date: Sat, 14 Jan 2023 16:47:18 +0000	[thread overview]
Message-ID: <20230114164718.4a77bfdb@jic23-huawei> (raw)
In-Reply-To: <20230110134323.543123-1-marten.lindahl@axis.com>

On Tue, 10 Jan 2023 14:43:20 +0100
Mårten Lindahl <marten.lindahl@axis.com> wrote:

> Hi!
> 
> I have made three patches to add support for proximity sensor
> interrupts with the vcnl4040 sensor.
> 
> The first two patches are minor restructuring of the current setup for
> interrupts since the probe function hardcodes it for vcnl4010 only.
> 
> The third patch adds support to configure proximity sensor interrupts
> and threshold limits for vcnl4040.
> 
> Kind regards
> Mårten Lindahl

Series applied to the togreg branch of iio.git. Initially pushed out as
testing so that the bots can take a poke at it before I make a mess
of Linux next if we missed something.

Thanks,

Jonathan

> 
> Changes in v3:
>  - Only register iio_trigger when there is an irq_thread function
> 
> Changes in v2:
>  - Make restructure of functions for interrupts and triggered buffer
>    in separate patch
>  - Add check for buffer_setup_ops
>  - Remove irq dependency for devm_iio_triggered_buffer_setup
>  - Change size of register variable and document it
>  - Use field definitions for read/write event_config
> 
> Mårten Lindahl (3):
>   iio: light: vcnl4000: Prepare for more generic setup
>   iio: light: vcnl4000: Make irq handling more generic
>   iio: light: vcnl4000: Add interrupt support for vcnl4040
> 
>  drivers/iio/light/vcnl4000.c | 479 ++++++++++++++++++++++++-----------
>  1 file changed, 328 insertions(+), 151 deletions(-)
> 


      parent reply	other threads:[~2023-01-14 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 13:43 [PATCH v3 0/3] iio: light: vcnl4000: Add vcnl4040 interrupt support Mårten Lindahl
2023-01-10 13:43 ` [PATCH v3 1/3] iio: light: vcnl4000: Prepare for more generic setup Mårten Lindahl
2023-01-10 13:43 ` [PATCH v3 2/3] iio: light: vcnl4000: Make irq handling more generic Mårten Lindahl
2023-01-15 17:41   ` andriy.shechenko
2023-01-16 23:06     ` Marten Lindahl
2023-01-10 13:43 ` [PATCH v3 3/3] iio: light: vcnl4000: Add interrupt support for vcnl4040 Mårten Lindahl
2023-01-15 17:38   ` andriy.shechenko
2023-01-16 17:32     ` Jonathan Cameron
2023-01-16 23:22       ` Marten Lindahl
2023-01-16 23:19     ` Marten Lindahl
2023-01-14 16:47 ` Jonathan Cameron [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=20230114164718.4a77bfdb@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=kernel@axis.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=marten.lindahl@axis.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