From: Jonathan Cameron <jic23@kernel.org>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: lars@metafoo.de, ang.iglesiasg@gmail.com,
andriy.shevchenko@linux.intel.com, linus.walleij@linaro.org,
semen.protsenko@linaro.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: iio: pressure: Fixes BMP38x and BMP390 SPI support
Date: Sat, 24 Feb 2024 16:30:51 +0000 [thread overview]
Message-ID: <20240224163051.3edcf102@jic23-huawei> (raw)
In-Reply-To: <20240219191359.18367-1-vassilisamir@gmail.com>
On Mon, 19 Feb 2024 20:13:59 +0100
Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
> According to the datasheet of BMP38x and BMP390 devices, for an SPI
> read operation the first byte that is returned needs to be dropped,
> and the rest of the bytes are the actual data returned from the
> sensor.
>
> Fixes: 8d329309184d ("iio: pressure: bmp280: Add support for BMP380 sensor family")
>
> Signed-off-by: Vasileios Amoiridis <vassilisamir@gmail.com>
Applied and marked for stable - with tweaks to header order and the space above
as per discussion.
> ---
> drivers/iio/pressure/bmp280-spi.c | 49 ++++++++++++++++++++++++++++++-
> 1 file changed, 48 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/pressure/bmp280-spi.c b/drivers/iio/pressure/bmp280-spi.c
> index e8a5fed07e88..1972014dca93 100644
> --- a/drivers/iio/pressure/bmp280-spi.c
> +++ b/drivers/iio/pressure/bmp280-spi.c
> @@ -8,6 +8,7 @@
> #include <linux/spi/spi.h>
> #include <linux/err.h>
> #include <linux/regmap.h>
> +#include <linux/bits.h>
>
> #include "bmp280.h"
>
> @@ -35,6 +36,33 @@ static int bmp280_regmap_spi_read(void *context, const void *reg,
> return spi_write_then_read(spi, reg, reg_size, val, val_size);
> }
>
> +static int bmp380_regmap_spi_read(void *context, const void *reg,
> + size_t reg_size, void *val, size_t val_size)
> +{
> + struct spi_device *spi = to_spi_device(context);
> + u8 rx_buf[4];
> + ssize_t status;
> +
> + /*
> + * Maximum number of consecutive bytes read for a temperature or
> + * pressure measurement is 3.
> + */
> + if (val_size > 3)
> + return -EINVAL;
> + /*
> + * According to the BMP3xx datasheets, for a basic SPI read opertion,
> + * the first byte needs to be dropped and the rest are the requested
> + * data.
> + */
> + status = spi_write_then_read(spi, reg, 1, rx_buf, val_size + 1);
> + if (status)
> + return status;
> +
> + memcpy(val, rx_buf + 1, val_size);
> +
> + return 0;
> +}
> +
> static struct regmap_bus bmp280_regmap_bus = {
> .write = bmp280_regmap_spi_write,
> .read = bmp280_regmap_spi_read,
> @@ -42,10 +70,19 @@ static struct regmap_bus bmp280_regmap_bus = {
> .val_format_endian_default = REGMAP_ENDIAN_BIG,
> };
>
> +static struct regmap_bus bmp380_regmap_bus = {
> + .write = bmp280_regmap_spi_write,
> + .read = bmp380_regmap_spi_read,
> + .read_flag_mask = BIT(7),
> + .reg_format_endian_default = REGMAP_ENDIAN_BIG,
> + .val_format_endian_default = REGMAP_ENDIAN_BIG,
> +};
> +
> static int bmp280_spi_probe(struct spi_device *spi)
> {
> const struct spi_device_id *id = spi_get_device_id(spi);
> const struct bmp280_chip_info *chip_info;
> + struct regmap_bus *bmp_regmap_bus;
> struct regmap *regmap;
> int ret;
>
> @@ -58,8 +95,18 @@ static int bmp280_spi_probe(struct spi_device *spi)
>
> chip_info = spi_get_device_match_data(spi);
>
> + switch (chip_info->chip_id[0]) {
> + case BMP380_CHIP_ID:
> + case BMP390_CHIP_ID:
> + bmp_regmap_bus = &bmp380_regmap_bus;
> + break;
> + default:
> + bmp_regmap_bus = &bmp280_regmap_bus;
> + break;
> + }
> +
> regmap = devm_regmap_init(&spi->dev,
> - &bmp280_regmap_bus,
> + bmp_regmap_bus,
> &spi->dev,
> chip_info->regmap_config);
> if (IS_ERR(regmap)) {
next prev parent reply other threads:[~2024-02-24 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 19:13 [PATCH] drivers: iio: pressure: Fixes BMP38x and BMP390 SPI support Vasileios Amoiridis
2024-02-19 19:42 ` Jonathan Cameron
2024-02-19 19:51 ` Vasileios Amoiridis
2024-02-20 13:51 ` Andy Shevchenko
2024-02-19 23:30 ` Angel Iglesias
2024-02-20 14:09 ` Andy Shevchenko
2024-02-20 17:46 ` Vasileios Amoiridis
2024-02-20 17:54 ` Andy Shevchenko
2024-02-20 17:55 ` Jonathan Cameron
2024-02-24 16:30 ` Jonathan Cameron [this message]
2024-03-06 18:08 ` Vasileios Amoiridis
2024-03-09 18:04 ` 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=20240224163051.3edcf102@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=semen.protsenko@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox