mbox series

[0/3] spi: fix spi-mux/spi_optimize_message() compatibility

Message ID 20240708-spi-mux-fix-v1-0-6c8845193128@baylibre.com (mailing list archive)
Headers show
Series spi: fix spi-mux/spi_optimize_message() compatibility | expand

Message

David Lechner July 9, 2024, 1:05 a.m. UTC
Since the spi-mux controller driver is doing unusual things with SPI
messages, it needs special handling with regard to spi_optimize_message
and friends.

The main fix along with a detailed explanation is in the second patch.

The first patch is another unrelated general fix that I noticed while
working on this.

And the third patch is not exactly related, but I needed it for the
particular peripheral driver I was using for testing the main fix.

I tested this for both cases when spi_optimize_message() is called to
pre-optimize a message and when it is not.

---
David Lechner (3):
      spi: don't unoptimize message in spi_async()
      spi: add defer_optimize_message controller flag
      spi: mux: set ctlr->bits_per_word_mask

 drivers/spi/spi-mux.c   |  2 ++
 drivers/spi/spi.c       | 20 +++++++++++++++++---
 include/linux/spi/spi.h |  4 ++++
 3 files changed, 23 insertions(+), 3 deletions(-)
---
base-commit: f42920e81a8f5f9fdf4a46b233ae14c22996e52b
change-id: 20240708-spi-mux-fix-6e2da5b5673d

Best regards,

Comments

Mark Brown July 10, 2024, 5:30 p.m. UTC | #1
On Mon, 08 Jul 2024 20:05:27 -0500, David Lechner wrote:
> Since the spi-mux controller driver is doing unusual things with SPI
> messages, it needs special handling with regard to spi_optimize_message
> and friends.
> 
> The main fix along with a detailed explanation is in the second patch.
> 
> The first patch is another unrelated general fix that I noticed while
> working on this.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] spi: don't unoptimize message in spi_async()
      commit: c86a918b1bdba78fb155184f8d88dfba1e63335d
[2/3] spi: add defer_optimize_message controller flag
      commit: ca52aa4c60f76566601b42e935b8a78f0fb4f8eb
[3/3] spi: mux: set ctlr->bits_per_word_mask
      commit: c8bd922d924bb4ab6c6c488310157d1a27996f31

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark