From: Jonathan Cameron <jic23@kernel.org>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: lars@metafoo.de, himanshujha199640@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Looijmans <mike.looijmans@topic.nl>,
David Frey <dpfrey@gmail.com>
Subject: Re: [PATCH v1 00/17] iio: chemical: bme680: Driver cleanup
Date: Sun, 2 Jun 2024 13:31:05 +0100 [thread overview]
Message-ID: <20240602133105.4334175d@jic23-huawei> (raw)
In-Reply-To: <20240527183805.311501-1-vassilisamir@gmail.com>
On Mon, 27 May 2024 20:37:48 +0200
Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
> This started as a series to add support for buffers and the new
> BME688 but it ended up being just a cleaning series. These might
> be quite some patches for such a thing but I feel that they are
> are well split, in order to allow for better review.
>
> The patches are mostly small changes but essential for the correct use
> of the driver. The first patches looked like fixes that should be
> marked for the stable. Patches [11,17/17] might be a bit bigger but 11/17
> is quite straightforward and 17/17 is basically a duplication of a
> very similar commit coming from the BMP280 driver [1].
>
> In general, the datasheet [2] of the driver is not very descriptive,
> and it redirects the user to the BME68x Sensor API [3]. All the things
> that were identified from the BME68x Sensor API have been marked with
> links to the original locations of the GitHub code. If this is too much
> and we don't want this type of information on the commit message, please
> let me know and I will fix it.
>
> [1]: https://lore.kernel.org/linux-iio/20240512230524.53990-1-vassilisamir@gmail.com/T/#mc6f814e9a4f8c2b39015909d174c7013b3648b9b
> [2]: https://www.bosch-sensortec.com/media/boschsensortec/downloads/datasheets/bst-bme680-ds001.pdf
> [3]: https://github.com/boschsensortec/BME68x_SensorAPI/tree/master
+CC Mike and David who have been active around this driver in the past.
>
> Vasileios Amoiridis (17):
> iio: chemical: bme680: Fix pressure value output
> iio: chemical: bme680: Fix calibration data variable
> iio: chemical: bme680: Fix overflows in compensate() functions
> iio: chemical: bme680: Fix sensor data read operation
> iio: chemical: bme680: Fix type in define
> iio: chemical: bme680: Add mutexes to guard read/write to device
> iio: chemical: bme680: Drop unnecessary casts and correct adc data
> types
> iio: chemical: bme680: Remove remaining ACPI-only stuff
> iio: chemical: bme680: Sort headers alphabetically
> iio: chemical: bme680: Remove duplicate register read
> iio: chemical: bme680: Use bulk reads for calibration data
> iio: chemical: bme680: Allocate IIO device before chip initialization
> iio: chemical: bme680: Add read buffers in DMA safe region
> iio: chemical: bme680: Modify startup procedure
> iio: chemical: bme680: Remove redundant gas configuration
> iio: chemical: bme680: Move forced mode setup in ->read_raw()
> iio: chemical: bme680: Refactorize reading functions
>
> drivers/iio/chemical/bme680.h | 39 +-
> drivers/iio/chemical/bme680_core.c | 643 ++++++++++++++---------------
> 2 files changed, 315 insertions(+), 367 deletions(-)
>
>
> base-commit: 409b6d632f5078f3ae1018b6e43c32f2e12f6736
prev parent reply other threads:[~2024-06-02 12:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 18:37 [PATCH v1 00/17] iio: chemical: bme680: Driver cleanup Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 01/17] iio: chemical: bme680: Fix pressure value output Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 02/17] iio: chemical: bme680: Fix calibration data variable Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 03/17] iio: chemical: bme680: Fix overflows in compensate() functions Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 04/17] iio: chemical: bme680: Fix sensor data read operation Vasileios Amoiridis
2024-06-02 12:41 ` Jonathan Cameron
2024-06-02 19:00 ` Vasileios Amoiridis
2024-06-03 19:23 ` Jonathan Cameron
2024-06-03 20:31 ` Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 05/17] iio: chemical: bme680: Fix type in define Vasileios Amoiridis
2024-06-02 12:41 ` Jonathan Cameron
2024-06-02 19:17 ` Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 06/17] iio: chemical: bme680: Add mutexes to guard read/write to device Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 07/17] iio: chemical: bme680: Drop unnecessary casts and correct adc data types Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 08/17] iio: chemical: bme680: Remove remaining ACPI-only stuff Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 09/17] iio: chemical: bme680: Sort headers alphabetically Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 10/17] iio: chemical: bme680: Remove duplicate register read Vasileios Amoiridis
2024-06-02 12:50 ` Jonathan Cameron
2024-06-02 19:25 ` Vasileios Amoiridis
2024-05-27 18:37 ` [PATCH v1 11/17] iio: chemical: bme680: Use bulk reads for calibration data Vasileios Amoiridis
2024-06-02 12:57 ` Jonathan Cameron
2024-06-02 19:30 ` Vasileios Amoiridis
2024-06-03 19:25 ` Jonathan Cameron
2024-06-03 20:30 ` Vasileios Amoiridis
2024-06-06 19:36 ` Jonathan Cameron
2024-05-27 18:38 ` [PATCH v1 12/17] iio: chemical: bme680: Allocate IIO device before chip initialization Vasileios Amoiridis
2024-05-27 18:38 ` [PATCH v1 13/17] iio: chemical: bme680: Add read buffers in DMA safe region Vasileios Amoiridis
2024-06-02 12:59 ` Jonathan Cameron
2024-06-02 19:33 ` Vasileios Amoiridis
2024-06-03 19:27 ` Jonathan Cameron
2024-05-27 18:38 ` [PATCH v1 14/17] iio: chemical: bme680: Modify startup procedure Vasileios Amoiridis
2024-06-02 13:01 ` Jonathan Cameron
2024-06-02 19:40 ` Vasileios Amoiridis
2024-05-27 18:38 ` [PATCH v1 15/17] iio: chemical: bme680: Remove redundant gas configuration Vasileios Amoiridis
2024-05-27 18:38 ` [PATCH v1 16/17] iio: chemical: bme680: Move forced mode setup in ->read_raw() Vasileios Amoiridis
2024-05-27 18:38 ` [PATCH v1 17/17] iio: chemical: bme680: Refactorize reading functions Vasileios Amoiridis
2024-06-02 13:04 ` Jonathan Cameron
2024-06-02 19:53 ` Vasileios Amoiridis
2024-06-02 12:31 ` 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=20240602133105.4334175d@jic23-huawei \
--to=jic23@kernel.org \
--cc=dpfrey@gmail.com \
--cc=himanshujha199640@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=vassilisamir@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.