public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Abhash Jha <abhashkumarjha123@gmail.com>
Cc: linux-iio@vger.kernel.org, anshulusr@gmail.com, lars@metafoo.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Threshold event and Sampling freq support for LTR390
Date: Sat, 28 Sep 2024 16:47:07 +0100	[thread overview]
Message-ID: <20240928164707.091fa5f7@jic23-huawei> (raw)
In-Reply-To: <20240914181246.504450-1-abhashkumarjha123@gmail.com>

On Sat, 14 Sep 2024 23:42:42 +0530
Abhash Jha <abhashkumarjha123@gmail.com> wrote:

> Hello,
> 
> The first patch adds support for configuring the Sampling frequency of
> the sensor. The available values for the sampling freqeuncy are provided
> by the `read_avail` callback and they are in miliHertz.
> 
> Then the second patch adds support for suspending and resuming
> the sensor by providing the necessary callbacks. And registering
> the ops with the driver.
> 
> The third patch in the series adds support for Threshold events and interrupts.
> Exposed rising and falling threshold events for both the channels. The events
> can be configured via the write_event_config callback. The desired rising or falling
> threshold value can be written to from userspace.
> 
> The fourth patch adds support for threshold interrupt persistance.
> It triggers when the UVS/ALS data is out of thresholds for a specific number
> of consecutive measurements.
> Exposed the IIO_EV_INFO_PERIOD attribute by which userspace can set the persistance
> value in miliseconds. The persistance period should be greater than or equal
> to the sampling period.

Applied with tweaks to the testing branch of iio.git which will be rebased
on rc1 once available.

Thanks,

Jonathan

> 
> Changes in v3:
> - Replace hardcoded mask values with GENMASK()
> - Minor refactoring
> - Code formatting changes
> 
> Changes in v2:
> - Added "linux/irq.h" include to fix `-Wimplicit-function-declaration`.
> - The above error was pointed during testing by kernel-test-robot
> 
> Thanks,
> Abhash
> 
> 
> Abhash Jha (4):
>   iio: light: ltr390: Added configurable sampling frequency support
>   iio: light: ltr390: Suspend and Resume support
>   iio: light: ltr390: Interrupts and threshold event support
>   iio: light: ltr390: Add interrupt persistance support
> 
>  drivers/iio/light/ltr390.c | 361 ++++++++++++++++++++++++++++++++++++-
>  1 file changed, 357 insertions(+), 4 deletions(-)
> 


      parent reply	other threads:[~2024-09-28 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 18:12 [PATCH v3 0/4] Threshold event and Sampling freq support for LTR390 Abhash Jha
2024-09-14 18:12 ` [PATCH v3 1/4] iio: light: ltr390: Added configurable sampling frequency support Abhash Jha
2024-09-14 18:12 ` [PATCH v3 2/4] iio: light: ltr390: Suspend and Resume support Abhash Jha
2024-09-28 15:36   ` Jonathan Cameron
2024-09-14 18:12 ` [PATCH v3 3/4] iio: light: ltr390: Interrupts and threshold event support Abhash Jha
2024-09-28 15:45   ` Jonathan Cameron
2024-09-14 18:12 ` [PATCH v3 4/4] iio: light: ltr390: Add interrupt persistance support Abhash Jha
2024-09-28 15: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=20240928164707.091fa5f7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=abhashkumarjha123@gmail.com \
    --cc=anshulusr@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.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