public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 6.6.y] iio: imu: inv_icm42600: fix spi burst write not supported
Date: Wed, 15 Jan 2025 11:32:07 +0100	[thread overview]
Message-ID: <2025011500-unmixable-duplex-9261@gregkh> (raw)
In-Reply-To: <20250113124638.252974-1-inv.git-commit@tdk.com>

On Mon, Jan 13, 2025 at 12:46:38PM +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 | 15 +++++++++++++++
>  drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c  |  3 ++-
>  3 files changed, 18 insertions(+), 1 deletion(-)

Did you test build this?

  parent reply	other threads:[~2025-01-15 10:32 UTC|newest]

Thread overview: 10+ 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 6.6-stable tree gregkh
2025-01-13 12:46 ` [PATCH 6.6.y] iio: imu: inv_icm42600: fix spi burst write not supported inv.git-commit
2025-01-13 23:09   ` Sasha Levin
2025-01-15 10:32   ` Greg KH [this message]
2025-01-15 10:50     ` Jean-Baptiste Maneyrol
2025-01-15 10:59       ` Greg KH
2025-01-15 14:02         ` Jean-Baptiste Maneyrol
2025-01-20 15:09           ` Greg KH
2025-01-13 13:53 ` [PATCH 6.6.y v2] " inv.git-commit
2025-01-13 23:09   ` Sasha Levin

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=2025011500-unmixable-duplex-9261@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox