From: Jonathan Cameron <jic23@kernel.org>
To: Alex Lanzano <lanzano.alex@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 1/1] iio: imu: bmi270: Add spi driver for bmi270 imu
Date: Thu, 10 Oct 2024 19:09:10 +0100 [thread overview]
Message-ID: <20241010190910.383f4489@jic23-huawei> (raw)
In-Reply-To: <20241002033628.681812-1-lanzano.alex@gmail.com>
On Tue, 1 Oct 2024 23:36:22 -0400
Alex Lanzano <lanzano.alex@gmail.com> wrote:
> Implement SPI driver for the Bosch BMI270 6-axis IMU. Provide raw read
> write access to acceleration and angle velocity measurements via the SPI
> interface on the device.
>
> Signed-off-by: Alex Lanzano <lanzano.alex@gmail.com>
Hi Alex,
Applied with one minor tweak. See below.
Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to poke at it and see if we missed anything.
Thanks,
Jonathan
p.s. Thought I'd sent this already - hence I actually applied this last weekend :(
> struct bmi270_data {
> diff --git a/drivers/iio/imu/bmi270/bmi270_core.c b/drivers/iio/imu/bmi270/bmi270_core.c
> index 8e45343d6472..638ce2c30d0e 100644
> --- a/drivers/iio/imu/bmi270/bmi270_core.c
> +++ b/drivers/iio/imu/bmi270/bmi270_core.c
> @@ -66,12 +66,6 @@ enum bmi270_scan {
> BMI270_SCAN_GYRO_Z,
> };
>
> -const struct regmap_config bmi270_regmap_config = {
> - .reg_bits = 8,
> - .val_bits = 8,
> -};
> -EXPORT_SYMBOL_NS_GPL(bmi270_regmap_config, IIO_BMI270);
> -
> static int bmi270_get_data(struct bmi270_data *bmi270_device,
> int chan_type, int axis, int *val)
> {
> @@ -90,7 +84,9 @@ static int bmi270_get_data(struct bmi270_data *bmi270_device,
> return -EINVAL;
> }
>
> - ret = regmap_bulk_read(bmi270_device->regmap, reg, &sample, sizeof(sample));
> + ret = regmap_bulk_read(bmi270_device->regmap, reg,
> + &sample,
> + sizeof(sample));
Trivial but this is an unrelated change. Possibly valid but doesn't belong
in this patch set. I'll drop it whilst applying.
> if (ret)
> return ret;
>
prev parent reply other threads:[~2024-10-10 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 3:36 [PATCH v2 1/1] iio: imu: bmi270: Add spi driver for bmi270 imu Alex Lanzano
2024-10-10 18:09 ` 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=20241010190910.383f4489@jic23-huawei \
--to=jic23@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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