From: Abhash Jha <abhashkumarjha123@gmail.com>
To: linux-iio@vger.kernel.org
Cc: jic23@kernel.org, lars@metafoo.de, linux-kernel@vger.kernel.org,
Abhash Jha <abhashkumarjha123@gmail.com>
Subject: [PATCH v3 0/3]
Date: Mon, 7 Oct 2024 20:49:44 +0530 [thread overview]
Message-ID: <20241007151947.58828-1-abhashkumarjha123@gmail.com> (raw)
Hello,
The first patch adds support for configuring the Sampling frequency
(inter-measurement period) of the sensor. The values should be provided
in milihertz. The default value for the inter-measurement period for
ALS is 10ms or 100000 mHz and for Range is 50ms or 20000 mHz.
The second patch adds support for interrupt based single shot reading.
We registered an irq_handler that fires everytime the data is ready.
And then we read the appropriate value in the `vl6180_measure` routine.
The third patch adds support for continuous mode in the sensor by using
buffers. We enable the sensor's continuous mode in the buffer_postenable
function depending on the `active_scan_mask`.
The continuous mode can be disabled by disabling the buffer.
Added a trigger to the device for the continuous mode. Also validating that
the device uses the internal trigger provided by us.
Changes in v2:
- Fixed `label followed by a declaration is a C23 extension [-Wc23-extensions]`
by moving the guard(mutex)(&data->lock) above the switch statement.
- The above error was pointed out during testing by kernel-test-robot
Changes in v3:
- Fixed race condition related to `reinit_completion`
- Used `iio_for_each_active_channel` instead of manually accessing `masklength`
- Accepting sampling frequency values in milihertz instead of miliseconds.
- Minor code refactoring.
Thanks,
Abhash Jha
Abhash Jha (3):
iio: light: vl6180: Add configurable inter-measurement period support
iio: light: vl6180: Added Interrupt support for single shot access
iio: light: vl6180: Add support for Continuous Mode
drivers/iio/light/vl6180.c | 255 ++++++++++++++++++++++++++++++++++---
1 file changed, 238 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2024-10-07 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:19 Abhash Jha [this message]
2024-10-07 15:19 ` [PATCH v3 1/3] iio: light: vl6180: Add configurable inter-measurement period support Abhash Jha
2024-10-07 15:19 ` [PATCH v3 2/3] iio: light: vl6180: Added Interrupt support for single shot access Abhash Jha
2024-10-07 15:19 ` [PATCH v3 3/3] iio: light: vl6180: Add support for Continuous Mode Abhash Jha
-- strict thread matches above, loose matches on Subject: below --
2012-11-26 15:19 [PATCH v3 0/3] Jacob Pan
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=20241007151947.58828-1-abhashkumarjha123@gmail.com \
--to=abhashkumarjha123@gmail.com \
--cc=jic23@kernel.org \
--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