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 v7 0/5] iio: pressure: bmp280: Add triggered buffer support and
Date: Mon, 13 May 2024 01:05:19 +0200 [thread overview]
Message-ID: <20240512230524.53990-1-vassilisamir@gmail.com> (raw)
Based on testing branch of iio.git
IMPORTANT NOTE: There are already upstreamed fixes for this driver [1], [2] and
there is an upcoming one [3]. They will probably conflict with the the last
three commits PATCH [3-5/5]. The solution should be quite trivial with minor
changes in these 3 patches. When it is deemed necessary I can resubmit the
patches or help with resolving the issue:
Changes in v7:
PATCH [1/5]:
- PATCH [5/9] of previous version
- Moved comments to correct locations and dropped unnecessary casting.
PATCH [2/5]:
- Used bmp580_nvmem_{read/write}_impl() functions for the read/write
operations and bmp580_nvmem_{read/write}() for applying the power
managent functions in order to keep correct order of mutex unlocking
and power management with the guard(mutex).
PATCH [4/5]:
- Used ARRAY_SIZE(bmpxxx_channels) for the .num_channels variable in the
bmp280_chip_info struct in order to make code better and more
maintainable
PATCH [5/5]:
- Adjusted changes for the addition of ARRAY_SIZE(bmpxxx_channels) in
the previous commit.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=546a4f4b5f4d930ea57f5510e109acf08eca5e87
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ca29ea4e4073b3caba750efe155b1bd4c597ca9
[3]: https://lore.kernel.org/linux-iio/043f2be49df3c11152aaf32fc5467ed43fd59faa.camel@gmail.com/
Previous versions:
v6: https://lore.kernel.org/linux-iio/20240508165207.145554-1-vassilisamir@gmail.com/
v5: https://lore.kernel.org/linux-iio/20240429190046.24252-1-vassilisamir@gmail.com/
v4: https://lore.kernel.org/linux-iio/20240407172920.264282-1-vassilisamir@gmail.com/
v3: https://lore.kernel.org/linux-iio/20240319002925.2121016-1-vassilisamir@gmail.com/
v2: https://lore.kernel.org/linux-iio/20240313174007.1934983-1-vassilisamir@gmail.com/
v1: https://lore.kernel.org/linux-iio/20240303165300.468011-1-vassilisamir@gmail.com/
Vasileios Amoiridis (5):
iio: pressure: bmp280: Refactorize reading functions
iio: pressure: bmp280: Introduce new cleanup routines
iio: pressure: bmp280: Generalize read_{temp,press,humid}() 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 | 1057 ++++++++++++++++++++--------
drivers/iio/pressure/bmp280-spi.c | 8 +-
drivers/iio/pressure/bmp280.h | 34 +-
4 files changed, 810 insertions(+), 291 deletions(-)
base-commit: 34d3aa6a60c8e0d053e8df5ff4a2b211951f06a6
--
2.25.1
next reply other threads:[~2024-05-12 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 23:05 Vasileios Amoiridis [this message]
2024-05-12 23:05 ` [PATCH v7 1/5] iio: pressure: bmp280: Refactorize reading functions Vasileios Amoiridis
2024-05-19 14:22 ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 2/5] iio: pressure: bmp280: Introduce new cleanup routines Vasileios Amoiridis
2024-05-19 14:24 ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 3/5] iio: pressure: bmp280: Generalize read_{temp,press,humid}() functions Vasileios Amoiridis
2024-05-19 14:28 ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 4/5] iio: pressure: bmp280: Add SCALE, RAW values in channels and refactorize them Vasileios Amoiridis
2024-05-19 14:30 ` Jonathan Cameron
2024-05-12 23:05 ` [PATCH v7 5/5] iio: pressure: bmp280: Add triggered buffer support Vasileios Amoiridis
2024-05-19 14:35 ` Jonathan Cameron
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=20240512230524.53990-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).