From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vasileios Amoiridis <vassilisamir@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, ang.iglesiasg@gmail.com,
579lpy@gmail.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: iio: pressure: Add SPI support for BMP38x and BMP390
Date: Thu, 15 Feb 2024 19:03:27 +0200 [thread overview]
Message-ID: <Zc5D35_4FdERZXe4@smile.fi.intel.com> (raw)
In-Reply-To: <20240215164332.506736-1-vassilisamir@gmail.com>
On Thu, Feb 15, 2024 at 05:43:32PM +0100, Vasileios Amoiridis wrote:
> According to the datasheet of BMP38x and BMP390 devices, in SPI
> operation, the first byte that returns after a read operation is
> garbage and it needs to be dropped and return the rest of the
> bytes.
Thank you for the patch, my comments below.
...
> +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 ret[BMP380_SPI_MAX_REG_COUNT_READ + 1];
> + ssize_t status;
> + u8 buf;
AFAIU this buffer is not DMA-capable.
> + memcpy(&buf, reg, reg_size);
I prefer to see a switch case with cases based on allowed sizes and proper
endianess accessors.
> + buf |= 0x80;
This is done by regmap, no?
> + /*
> + * According to the BMP380, BMP388, BMP390 datasheets, for a basic
> + * read operation, after the write is done, 2 bytes are received and
> + * the first one has to be dropped. The 2nd one is the requested
> + * value.
> + */
> + status = spi_write_then_read(spi, &buf, 1, ret, val_size + 1);
sizeof() ?
> + if (status)
> + return status;
> + memcpy(val, ret + 1, val_size);
As per above.
> + return 0;
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-15 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 16:43 [PATCH] drivers: iio: pressure: Add SPI support for BMP38x and BMP390 Vasileios Amoiridis
2024-02-15 17:03 ` Andy Shevchenko [this message]
2024-02-16 11:05 ` Jonathan Cameron
2024-02-16 13:29 ` Vasileios Amoiridis
2024-02-15 17:20 ` Angel Iglesias
2024-02-16 11:18 ` Jonathan Cameron
2024-02-16 13:26 ` Vasileios Amoiridis
2024-02-16 15:47 ` Jonathan Cameron
2024-02-16 16:40 ` 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=Zc5D35_4FdERZXe4@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=579lpy@gmail.com \
--cc=ang.iglesiasg@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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