From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: jic23@kernel.org, lars@metafoo.de
Cc: andriy.shevchenko@linux.intel.com, ang.iglesiasg@gmail.com,
mazziesaccount@gmail.com, ak@it-klinger.de,
petre.rodan@subdimension.ro, phil@raspberrypi.com,
579lpy@gmail.com, linus.walleij@linaro.org,
semen.protsenko@linaro.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vasileios Amoiridis <vassilisamir@gmail.com>
Subject: [PATCH v8 0/3] Driver cleanup and triggered buffer support
Date: Tue, 18 Jun 2024 01:05:37 +0200 [thread overview]
Message-ID: <20240617230540.32325-1-vassilisamir@gmail.com> (raw)
Based on current testing branch.
Changes in v8:
Patch 1/3:
- Changes in bmp580_read_temp() in order to incorporate the fix that was
introduced in [1].
Patch 3/3:
- Splitted bmp280_trigger_handler to bm(p/e)_trigger_handler as it was
mentioned in v7 comment.
- Added the sign_extend32() from the fix in [1] to the
bmp580_buffer_handler() as well.
These commits were dropped since there was a conflict with a fix for that
driver. Link to conversation [2].
Version 7: https://lore.kernel.org/linux-iio/20240512230524.53990-1-vassilisamir@gmail.com/
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0f0f6306617cb4b6231fc9d4ec68ab9a56dba7c0
[2]: https://lore.kernel.org/linux-iio/20240602201200.30418-1-ajarizzo@gmail.com/
Vasileios Amoiridis (3):
iio: pressure: bmp280: Generalize read_*() functions
iio: pressure: bmp280: Add SCALE, RAW values in channels and
refactorize them
iio: pressure: bmp280: Add triggered buffer support
drivers/iio/pressure/Kconfig | 2 +
drivers/iio/pressure/bmp280-core.c | 627 ++++++++++++++++++++++++-----
drivers/iio/pressure/bmp280-spi.c | 8 +-
drivers/iio/pressure/bmp280.h | 34 +-
4 files changed, 568 insertions(+), 103 deletions(-)
base-commit: 7db8a847f98caae68c70bdab9ba92d1af38e5656
--
2.25.1
next reply other threads:[~2024-06-17 23:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 23:05 Vasileios Amoiridis [this message]
2024-06-17 23:05 ` [PATCH v8 1/3] iio: pressure: bmp280: Generalize read_*() functions Vasileios Amoiridis
2024-06-22 9:28 ` Jonathan Cameron
2024-06-22 12:19 ` Vasileios Amoiridis
2024-06-23 16:23 ` Jonathan Cameron
2024-06-23 17:18 ` Vasileios Amoiridis
2024-06-25 20:44 ` Jonathan Cameron
2024-06-26 13:41 ` Vasileios Amoiridis
2024-06-24 4:26 ` Adam Rizkalla
2024-06-26 13:38 ` Vasileios Amoiridis
2024-06-17 23:05 ` [PATCH v8 2/3] iio: pressure: bmp280: Add SCALE, RAW values in channels and refactorize them Vasileios Amoiridis
2024-06-17 23:05 ` [PATCH v8 3/3] iio: pressure: bmp280: Add triggered buffer support Vasileios Amoiridis
2024-06-22 9:40 ` Jonathan Cameron
2024-06-22 12:32 ` Vasileios Amoiridis
2024-06-22 14:09 ` Vasileios Amoiridis
2024-06-23 16:26 ` Jonathan Cameron
2024-06-23 17:19 ` Vasileios Amoiridis
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=20240617230540.32325-1-vassilisamir@gmail.com \
--to=vassilisamir@gmail.com \
--cc=579lpy@gmail.com \
--cc=ak@it-klinger.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=petre.rodan@subdimension.ro \
--cc=phil@raspberrypi.com \
--cc=semen.protsenko@linaro.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