Changes in Makefile

307b9ddbbcf987db77d52da6f9ff5b4096ac9599 - Merge tag 'spi-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi

Wed, 19 Aug 2026 18:47:41 +0200

Merge tag 'spi-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spiPull spi updates from Mark Brown: "Along with a lot of driver specific work we've got a couple of core features here. The bigger one is that we've now got support for instantiating devices from sysfs similarly to how it's already done for I2C, this is used with development boards with non-enumerable expansion headers since SPI devices need to be manually specified. We also have support for the DQS signal on higher end flash devices. - Support for instantiating devices from sysfs, useful for development boards with non-enumerable plugin modules, from Vishwaroop A. - Support for DQS in spi-mem, an additional signal used by flash devices to avoid clock skew from Miquel Raynal. - Support for more advanced SPI modes on DesignWare controllers from Sudip Mukherjee. - Changes from Jisheng Zhang to update to modern methods of specifying the PM callbacks. - Fixes for DMA mapping error handling, plus KUnit tests for this, from Honghui Jiang. - Substantial cleanup and performance work in the nxp-spi driver. - Support for Microchip LAN969x, Nuvoton MA35D1 QSPI, Qualcomm SA8255p and SA8797P, and StarFive JHB100 SFC"* tag 'spi-v7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi: (132 commits) spi: Add KUnit coverage for DMA mapping error paths spi: Clear current DMA devices when unmapping a message spi: Move __spi_unmap_msg() before __spi_map_msg() spi: Fix DMA mapping ownership on partial map failure spi: dt-bindings: sun6i: Add compatibles for A733's SPI controllers spi: ma35d1-qspi: Use the existing update helper spi: ma35d1-qspi: Add DTR support spi: ma35d1-qspi: Allow several command bytes spi: ma35d1-qspi: Move speed setting to bus configuration spi: ma35d1-qspi: Remove redundant reset operation spi: dw: Remove shadowed dws in dw_spi_setup() spi: img-spfi: don't disable runtime PM on DMA deferred probe spi: mtk-nor: Propagate errors from IRQ request spi: mtk-nor: Propagate errors from optional IRQ lookup spi: spi-qpic-snand: Handle Macronix quad read opcode 0x6b spi: spi-qpic-snand: add quad mode support spi: spi-qpic-snand: move command mapping helper spi: hisi-sfc-v3xx: Propagate errors from optional IRQ lookup spi: meson-spifc: use devm_pm_runtime_set_active_enabled spi: sprd-adi: Fix probe succeeding without registering the controller ... List of files: /linux/drivers/spi/tests/Makefile

23688febe4b44b10f4b454eb1cde0ba379a84119 - spi: Fix DMA mapping ownership on partial map failure

Fri, 14 Aug 2026 17:48:53 +0200

spi: Fix DMA mapping ownership on partial map failureHonghui Jiang says:A partial DMA mapping failure can leave per-transfer mapping flags setwhile cur_{tx,rx}_dma_dev are NULL or still refer to the devices usedfor an earlier message. The subsequent cleanup may then unmap atransfer with a NULL or stale device.Before commit e289df82344f ("spi: Rework per message DMA mapped flag tobe per transfer"), partial-failure handling was already incomplete, but__spi_unmap_msg() was gated by cur_msg_mapped, which was set only afterthe whole message mapped successfully. Earlier mappings could leak, butcleanup could not unmap them with an unpublished device. Theper-transfer conversion removed that gate: mapping flags can now remainset while cur_{tx,rx}_dma_dev are still unpublished, turning the leakinto a NULL- or stale-device unmap regression.Patch 1 publishes the mapping devices before the loop and unwinds everyfailure through __spi_unmap_msg(). It keeps the forward declaration soit is independently buildable and straightforward to backport. Patch 2then removes the declaration by moving __spi_unmap_msg() above__spi_map_msg(). Patch 3 clears the current DMA device pointers once themessage has been unmapped, while leaving them intact during partial-mapunwind and DMA-to-PIO fallback. Patch 4 adds the DMA mapping KUnit suiteas a separate translation unit.Only patch 1 is a stable candidate; patches 2 through 4 are follow-upcleanup and test changes for mainline.Testing:- Patch 1 builds independently with the x86_64 reproducer configuration.- The spi_dma KUnit suite passes all four cases on x86_64 and UML. Moving the DMA device assignments back after the mapping loop makes both failure-path cases fail.- The default and all-tests KUnit configurations both select the suite.- All four reproducer cases complete without an oops when run as the first message, and map/unmap counts are balanced after a successful first message.- After message cleanup, cur_{tx,rx}_dma_dev are NULL.v1: https://lore.kernel.org/r/20260805151456.756579-1-jiang_hh2019@163.comLink: https://patch.msgid.link/20260814031419.43378-1-jiang_hh2019@163.com List of files: /linux/drivers/spi/tests/Makefile

9b81a87c5244bc139357460a262d4536226ba41d - spi: Add KUnit coverage for DMA mapping error paths

Fri, 14 Aug 2026 05:14:18 +0200

spi: Add KUnit coverage for DMA mapping error pathsAdd KUnit tests for the __spi_map_msg() error paths. The tests verifythat a later TX or RX mapping failure clears the mapping state ofearlier transfers and leaves cur_{tx,rx}_dma_dev identifying thecurrent mapping device.A zero-length transfer causes sg_alloc_table() to return -EINVAL,providing deterministic failure injection without test hooks.Additional cases cover successful map/unmap and a message whichrequires no mapping.Build the DMA suite as a separate translation unit, exposing the twointernal mapping helpers only for KUnit through the local internalheader. Enable SPI in the default and all-tests KUnit configurations sothe suite is exercised there.Signed-off-by: Honghui Jiang Reviewed-by: Andy Shevchenko Link: https://patch.msgid.link/20260814031419.43378-5-jiang_hh2019@163.comSigned-off-by: Mark Brown List of files: /linux/drivers/spi/tests/Makefile