From: Greg KH <gregkh@linuxfoundation.org>
To: inv.git-commit@tdk.com
Cc: stable@vger.kernel.org,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 5.15.y] iio: imu: inv_icm42600: fix spi burst write not supported
Date: Mon, 20 Jan 2025 16:12:41 +0100 [thread overview]
Message-ID: <2025012012-drearily-bonding-0904@gregkh> (raw)
In-Reply-To: <20250113131918.128606-1-inv.git-commit@tdk.com>
On Mon, Jan 13, 2025 at 01:19:18PM +0000, inv.git-commit@tdk.com wrote:
> From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
>
> Burst write with SPI is not working for all icm42600 chips. It was
> only used for setting user offsets with regmap_bulk_write.
>
> Add specific SPI regmap config for using only single write with SPI.
>
> Fixes: 9f9ff91b775b ("iio: imu: inv_icm42600: add SPI driver for inv_icm42600 driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> Link: https://patch.msgid.link/20241112-inv-icm42600-fix-spi-burst-write-not-supported-v2-1-97690dc03607@tdk.com
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> (cherry picked from commit c0f866de4ce447bca3191b9cefac60c4b36a7922)
> ---
> drivers/iio/imu/inv_icm42600/inv_icm42600.h | 1 +
> drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 12 ++++++++++++
> drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c | 3 ++-
> 3 files changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600.h b/drivers/iio/imu/inv_icm42600/inv_icm42600.h
> index 995a9dc06521..f5df2e13b063 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600.h
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600.h
> @@ -360,6 +360,7 @@ struct inv_icm42600_state {
> typedef int (*inv_icm42600_bus_setup)(struct inv_icm42600_state *);
>
> extern const struct regmap_config inv_icm42600_regmap_config;
> +extern const struct regmap_config inv_icm42600_spi_regmap_config;
> extern const struct dev_pm_ops inv_icm42600_pm_ops;
>
> const struct iio_mount_matrix *
> diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> index ca85fccc9839..a562d7476955 100644
> --- a/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> +++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_core.c
> @@ -43,6 +43,18 @@ const struct regmap_config inv_icm42600_regmap_config = {
> };
> EXPORT_SYMBOL_GPL(inv_icm42600_regmap_config);
>
> +/* define specific regmap for SPI not supporting burst write */
> +const struct regmap_config inv_icm42600_spi_regmap_config = {
> + .name = "inv_icm42600",
Why does just this one have the .name field set?
I've taken the backports you did for the other branches here, if you
really need .name set please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-20 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 9:57 FAILED: patch "[PATCH] iio: imu: inv_icm42600: fix spi burst write not supported" failed to apply to 5.15-stable tree gregkh
2025-01-13 13:19 ` [PATCH 5.15.y] iio: imu: inv_icm42600: fix spi burst write not supported inv.git-commit
2025-01-13 23:09 ` Sasha Levin
2025-01-20 15:12 ` Greg KH [this message]
2025-01-21 10:56 ` Jean-Baptiste Maneyrol
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=2025012012-drearily-bonding-0904@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=inv.git-commit@tdk.com \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=stable@vger.kernel.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 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.