From: Joseph CT Chan <jctchan@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, David Lechner <dlechner@baylibre.com>,
Bart Van Assche <bvanassche@acm.org>,
Conor Dooley <conor.dooley@microchip.com>,
Joseph CT Chan <josephctchan@google.com>
Subject: [PATCH v2 0/5] spi: lock context annotations
Date: Tue, 3 Nov 2026 22:55:17 +0000 [thread overview]
Message-ID: <20261103225522.3643901-1-jctchan@gmail.com> (raw)
From: Joseph CT Chan <josephctchan@google.com>
Hi Mark,
These are Bart Van Assche's patches, which I am carrying for him. They
add Clang lock context annotations for the SPI bus_lock_mutex, spi-mem
and microchip-core-qspi, split spi_write_then_read() so its buffer lock
can be checked, and turn on context analysis for drivers/spi and its
KUnit tests.
Tested by building with Clang 23.1.4 (kernel.org prebuilt toolchain)
and CONFIG_WARN_CONTEXT_ANALYSIS=y, with and without the other three
series applied, and running the SPI KUnit tests on ARCH=um. Not tested
on hardware.
Changes in v2:
- Split out of the v1 14-patch series, as David suggested. No code
changes.
v1: https://lore.kernel.org/all/20261102163023.2574632-1-jctchan@gmail.com/
This series depends on the SPI core series ("spi: unoptimize message
when queuing it fails" v2), because patch 5 touches the KUnit Makefile
that series adds to. It applies before or after the spi-mux and
spi-ti-qspi series.
SPI core series v2: https://lore.kernel.org/linux-spi/20261103224753.3610049-1-jctchan@gmail.com/
Please consider this patch series for the next merge window.
Thanks,
Joseph
Bart Van Assche (5):
spi: Split spi_write_then_read()
spi: Add lock context annotations for bus_lock_mutex
spi: spi-mem: Add lock context annotations
spi: microchip-core-qspi: Add lock context annotations
spi: Enable lock context analysis
drivers/spi/Makefile | 2 +
drivers/spi/spi-mem.c | 4 ++
drivers/spi/spi-microchip-core-qspi.c | 6 ++
drivers/spi/spi.c | 100 +++++++++++++++-----------
drivers/spi/tests/Makefile | 2 +
include/linux/spi/spi.h | 12 ++--
6 files changed, 80 insertions(+), 46 deletions(-)
base-commit: c339f4010dea8b0d754f84ace70cd1b089878ef8
prerequisite-patch-id: 6999a3baa2d32de8fa42f2626a845fe3cb63b0b2
prerequisite-patch-id: 686a62b9223209bf1e83740a0874e20d7607f69a
--
2.56.0.385.gac671c819a-goog
next reply other threads:[~2026-11-03 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:55 Joseph CT Chan [this message]
2026-11-03 22:55 ` [PATCH v2 1/5] spi: Split spi_write_then_read() Joseph CT Chan
2026-11-03 22:55 ` [PATCH v2 2/5] spi: Add lock context annotations for bus_lock_mutex Joseph CT Chan
2026-11-03 22:55 ` [PATCH v2 3/5] spi: spi-mem: Add lock context annotations Joseph CT Chan
2026-11-03 22:55 ` [PATCH v2 4/5] spi: microchip-core-qspi: " Joseph CT Chan
2026-11-03 22:55 ` [PATCH v2 5/5] spi: Enable lock context analysis Joseph CT Chan
2026-11-04 14:46 ` [PATCH v2 0/5] spi: lock context annotations Mark Brown
2026-11-05 4:03 ` Joseph CT Chan
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=20261103225522.3643901-1-jctchan@gmail.com \
--to=jctchan@gmail.com \
--cc=broonie@kernel.org \
--cc=bvanassche@acm.org \
--cc=conor.dooley@microchip.com \
--cc=dlechner@baylibre.com \
--cc=josephctchan@google.com \
--cc=linux-spi@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