* [PATCH v14 0/3] spi: pxa2xx: MacBook8,1 quirk, runtime PM, and LPSS S3 resume state fixes
@ 2026-07-18 16:06 Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1 Shih-Yuan Lee
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Shih-Yuan Lee @ 2026-07-18 16:06 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-spi, linux-kernel, Shih-Yuan Lee
Hi Mark,
This 3-patch series resolves issues in the spi-pxa2xx host controller driver
related to Intel LPSS SPI controllers and the Apple MacBook8,1.
Patch 1 moves the forced PIO mode quirk for the Apple MacBook8,1 LPSS SPI
controller from the client driver (applespi) to the host controller PCI glue
driver (spi-pxa2xx-pci) where it belongs.
Patch 2 fixes runtime PM and interrupt handling in PIO mode: when DMA is
disabled, aggressive runtime clock gating causes PCIe Completion Timeouts on
subsequent MMIO accesses. It scopes autosuspend lockout strictly to LPSS controllers,
tracks clock state to avoid disable underflows, protects shared IRQ handling using
drv_data->suspended and drv_data->clk_enabled, preserves the if (!pm_runtime_suspended(dev))
check in suspend/resume to avoid PM state desynchronization on non-LPSS SoCs, and
uses pm_runtime_put_sync() upon driver remove to correctly synchronize the PM state
machine to RPM_SUSPENDED.
Patch 3 fixes S3 suspend/resume for Intel LPSS SPI controllers. The LPSS
power domain is fully removed across S3, losing all private register state.
Accessing MMIO on resume while the block is held in reset causes a PCIe Completion
Timeout and a watchdog system reset. To fix this, we save the LPSS private
registers in struct driver_data during suspend, de-assert resets first on
resume, and restore the saved registers.
Changes in v14:
- Addressed feedback from Sashiko review on the v13 patchset for Patch 2:
- Updated commit message text for Patch 2 to accurately reflect that ssp_int()
uses drv_data->suspended and drv_data->clk_enabled instead of pm_runtime_get_if_active().
- Clarified in commit message that active SPI transfers hold a PM reference via
spi_controller.auto_runtime_pm (pm_runtime_get_sync()), preventing autosuspend
from racing while an IRQ handler is reading/writing FIFO registers.
- Clarified teardown ordering: pxa_ssp_disable() disables hardware interrupt generation
first, followed by setting drv_data->suspended = true and calling synchronize_irq(),
ensuring in-flight IRQ handlers drain completely before clock gating.
Changes in v13:
- Addressed feedback from Sashiko review on the v12 patchset for Patch 2:
- Removed pm_runtime_get_if_active() check from ssp_int(). During PM state
transitions (such as RPM_SUSPENDING or RPM_RESUMING), pm_runtime_get_if_active()
returns 0 because the state is not RPM_ACTIVE. Returning IRQ_NONE during transition
without clearing a level-triggered interrupt would cause the interrupt controller
to endlessly re-invoke the handler in a loop.
- Rely on drv_data->suspended and drv_data->clk_enabled in ssp_int() instead.
If the clock is enabled (drv_data->clk_enabled == true), MMIO reads are 100% safe
and will not cause PCIe Completion Timeouts. If the clock is disabled or the device
is suspended, ssp_int() immediately returns IRQ_NONE to prevent unclocked access.
Changes in v12:
- Addressed feedback from Sashiko review on the v11 patchset for Patch 2:
- Preserved the if (!pm_runtime_suspended(dev)) check prior to enabling/disabling
the clock in pxa2xx_spi_suspend() and pxa2xx_spi_resume(). On non-LPSS platforms,
if a device was runtime suspended prior to system sleep, unconditionally enabling
its hardware clock during system resume forced the clock ON while the PM core
retained RPM_SUSPENDED. Restoring this check prevents PM state desynchronization,
avoiding power leaks on non-LPSS platforms.
Changes in v11:
- Addressed feedback from Sashiko review on the v10 patchset for Patch 2:
- Replaced pm_runtime_put_noidle() with pm_runtime_put_sync() in pxa2xx_spi_remove().
Using pm_runtime_put_noidle() dropped usage count without executing the runtime_suspend
callback or updating the device runtime status, leaving it stuck in RPM_ACTIVE. This
permanently leaked an active child count on the parent LPSS power domain, preventing
the parent from entering low-power runtime suspend. Switching to pm_runtime_put_sync()
ensures the runtime PM state machine properly transitions to RPM_SUSPENDED upon driver
unbind.
Changes in v10:
- Addressed feedback from Sashiko review on the v9 patchset:
- Fixed ssp_int() by explicitly returning IRQ_NONE when pm_runtime_get_if_active()
returns 0 (device inactive or suspending). This prevents reading SSSR and MMIO
registers when the hardware is powered down or in power transition.
- Resolved PM usage counter leak and double-increment for PIO mode devices. Removed
the redundant/unconditional pm_runtime_get_noresume() in pxa2xx_spi_probe() and
moved the single pm_runtime_get_noresume() call to occur strictly after
spi_register_controller() succeeds.
Changes in v9:
- Separated the original "disable DMA and fix runtime PM" patch into two distinct commits:
1. spi: pxa2xx: disable DMA for Apple MacBook8,1 (PCI glue DMI quirk)
2. spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode (core driver PM/IRQ fixes)
- Condensed commit messages for Patches 2 and 3 for clarity and brevity.
- Fixed checkpatch.pl warning regarding unnecessary braces in pxa2xx_spi_remove().
- Addressed feedback from Sashiko review on the v8 patchset:
- Scoped pm_runtime_get_noresume() in pxa2xx_spi_probe() and pm_runtime_put_noidle()
in remove/error paths using is_lpss_ssp(drv_data). This locks out autosuspend
for LPSS controllers operating in PIO mode without causing power regressions on
non-LPSS platforms (e.g. PXA25x, Intel Quark, CE4100) operating in PIO mode.
- Guarded MMIO accesses in pxa2xx_spi_runtime_suspend() with a drv_data->clk_enabled
check. If the clock has already been turned off (e.g. in pxa2xx_spi_remove() or
resume error path), runtime suspend skips hardware writes, avoiding unclocked
MMIO accesses and PCIe Completion Timeouts if runtime PM triggers after teardown.
- Cleaned up pxa2xx_spi_pci_can_dma() signature in spi-pxa2xx-pci.c by removing the
redundant `bool verbose` parameter.
Changes in v8:
- Addressed feedback from Sashiko review on the v7 patchset:
- Fixed runtime PM resume interrupt storm in ssp_int() by checking drv_data->clk_enabled
instead of pm_runtime_get_if_active() == 0.
- Fixed PM disabled configuration (CONFIG_PM=n) support in ssp_int() by avoiding
active <= 0 early returns.
- Reordered suspend and remove sequences to invoke pxa_ssp_disable() before setting
drv_data->suspended = true and synchronizing the IRQ, closing a race window
where level-triggered interrupts could cause a storm.
- Masked hardware interrupt generation in pxa2xx_spi_runtime_suspend() via
pxa_ssp_disable() to prevent unexpected interrupts during clock enable.
- Avoided PCIe Completion Timeout system hangs on newer LPSS platforms (SPT, BXT, CNL)
by introducing pxa2xx_spi_need_lpss_restore() to restrict MMIO save/restore
loops to LPT, BYT, and BSW platforms (which lack an MFD parent).
- Fixed compiler error in pxa2xx_spi_probe() due to unused label.
Changes in v7:
- Addressed feedback from Sashiko review on the v6 patchset:
- Fixed a race condition during probe by moving the request_irq() call after
the clock is enabled and the suspended flag is cleared. This prevents an early
shared interrupt from asserting and triggering an interrupt storm before the clock
is active to allow clearing it.
- Rectified the teardown sequence in pxa2xx_spi_remove(): first set drv_data->suspended
to true and disable SSP hardware-level interrupt generation (pxa_ssp_disable()), then call
synchronize_irq() to wait for in-flight interrupt handlers to complete, free the
IRQ, and only then disable the clocks. This eliminates both post-clock-disable MMIO
accesses and unhandled shared hardware interrupt storms.
- Clarified that the unconditional MMIO register access in pxa2xx_spi_suspend()
is safe because pm_runtime_resume_and_get() is invoked at the very beginning of the
suspend callback, guaranteeing the LPSS device is active and clocked during register
disabling/saving.
- Added spi_controller_resume() recovery to the error path of spi_controller_suspend()
in pxa2xx_spi_suspend() to prevent the controller from remaining permanently disabled
in the event system suspend is aborted.
Changes in v6:
- Addressed feedback from Sashiko review on the v5 patchset:
- Added a synchronize_irq() call to the spi_controller_resume() error path in
pxa2xx_spi_resume(). This ensures any concurrent shared interrupt handlers
(which might execute because drv_data->suspended = false was set earlier)
finish executing before we disable the clock, preventing PCIe timeouts.
- Checked and confirmed that active == 0 is the correct check in ssp_int(). If
Runtime PM is disabled, pm_runtime_get_if_active() returns a negative error
code (like -EINVAL). Changing this check to active <= 0 would cause a
regression on non-PM configurations because the handler would always return
IRQ_NONE. Under disabled Runtime PM, the hardware clock is kept constantly
active, so it is safe to proceed and read registers when active < 0.
Changes in v5:
- Reverted runtime PM configuration in spi-pxa2xx-pci.c to be unconditional.
This prevents the usage count from leaking by +1 on unbind for PIO mode,
while letting pxa2xx_spi_probe()'s pm_runtime_get_noresume() and
pxa2xx_spi_remove()'s pm_runtime_put_noidle() handle the permanent
autosuspend lockout for PIO devices symmetrically.
- Removed the pm_runtime_forbid() call from pxa2xx_spi_remove(). This resolves
reference leaks for non-PCI platform devices where pm_runtime_allow() was
never called during probe.
- Delayed clearing the drv_data->suspended flag on resume until after LPSS reset
deassertion and private register restoration are complete. This prevents a
shared interrupt from firing during resume and attempting to read the SSSR
register while the LPSS block is still held in reset.
- Set drv_data->suspended = true on spi_controller_resume() failure path in
pxa2xx_spi_resume(). This ensures that subsequent shared interrupts do not
attempt register access once the clock is disabled.
Changes in v4:
- Track clock state using drv_data->clk_enabled via pxa2xx_spi_clk_enable() and
pxa2xx_spi_clk_disable() helper functions. This guarantees clock enable/disable
symmetry, preventing clock disable count underflows and framework warnings on S3
resume or runtime autosuspend error paths.
- Introduce drv_data->suspended flag to protect MMIO access in ssp_int() during
system suspend and runtime suspend transition windows.
- Initialize drv_data->suspended = true early in probe(), clearing it only after
the clock is successfully enabled. This completely prevents shared interrupt
handler races during device probe when the clock is still off.
- Call synchronize_irq() after setting drv_data->suspended = true in suspend and
runtime_suspend. This ensures any running shared interrupt handlers finish
executing before the clock is physically turned off.
Changes in v3:
- Avoid PM reference leaks on probe bind/unbind cycle by keeping probe PM
configuration symmetric.
- Prevent userspace (PowerTOP, udev) from overriding runtime PM settings when
DMA is disabled by holding a PM reference via pm_runtime_get_noresume()
in pxa2xx_spi_probe() and dropping it in remove/error paths.
- Check device status in the shared interrupt handler ssp_int() using
pm_runtime_get_if_active() instead of pm_runtime_suspended(). If the device is
suspending (RPM_SUSPENDING) or suspended, ssp_int() immediately returns
IRQ_NONE to avoid reading unclocked MMIO registers during power transition.
- Adjust the driver teardown order in pxa2xx_spi_remove() and probe error paths:
always call free_irq() to unregister the handler before calling
clk_disable_unprepare() to turn off the clock, preventing concurrent
interrupts from reading registers while the clock is disabled.
- Avoid duplicate can-DMA pci_info() logging by checking the pre-computed
enable_dma status in probe and passing a verbose flag to can_dma().
Changes in v2:
- Addressed feedback from Mark Brown on the original v1 series.
- Used drv_data->lpss_base together with relative offsets rather than
hardcoding absolute MMIO offsets that vary between LPSS IP revisions.
- Moved the register save block in suspend to after the controller is quiesced
(after spi_controller_suspend() and pxa_ssp_disable()).
- Store the context array lpss_priv_ctx[6] inside struct driver_data instead of
struct pxa2xx_spi_controller. This keeps the changes entirely local to the
core driver, preventing symbol version mismatches (disagrees about version
of symbol) for other subsystem components (e.g., spi-pxa2xx-platform.ko).
- Restrict the save/restore loop to the first 6 LPSS private registers
(offsets 0x00 to 0x14). Offsets beyond 0x14 (except CS control at 0x18, which is
re-initialised by lpss_ssp_setup()) are reserved/unimplemented on LPT
platforms (such as MacBook8,1), and writing to them triggers a PCIe
Completion Timeout causing a system freeze.
- Added named constants for LPSS_PRIV_RESETS and the de-assert value.
- Wrapped S3 suspend/resume with pm_runtime_resume_and_get() and
pm_runtime_put_autosuspend() respectively.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=108331
Shih-Yuan Lee (3):
spi: pxa2xx: disable DMA for Apple MacBook8,1
spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode
spi: pxa2xx: restore LPSS private register state on S3 resume
drivers/spi/spi-pxa2xx-pci.c | 35 ++++-
drivers/spi/spi-pxa2xx.c | 226 +++++++++++++++++++++++++++++------
drivers/spi/spi-pxa2xx.h | 4 +
3 files changed, 224 insertions(+), 41 deletions(-)
--
2.39.5
^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1
2026-07-18 16:06 [PATCH v14 0/3] spi: pxa2xx: MacBook8,1 quirk, runtime PM, and LPSS S3 resume state fixes Shih-Yuan Lee
@ 2026-07-18 16:07 ` Shih-Yuan Lee
2026-07-18 20:01 ` Mark Brown
2026-07-18 16:07 ` [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 3/3] spi: pxa2xx: restore LPSS private register state on S3 resume Shih-Yuan Lee
2 siblings, 1 reply; 6+ messages in thread
From: Shih-Yuan Lee @ 2026-07-18 16:07 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-spi, linux-kernel, Shih-Yuan Lee
On MacBook8,1 (early 2015 12" MacBook), the LPSS SPI controller at
00:15.4 suffers from hardware DMA handshake failures and interrupt
routing bugs, causing keyboard/touchpad transactions to fail when
DMA is enabled.
Move the forced PIO mode DMI quirk to spi-pxa2xx-pci.c (the LPSS host
controller PCI glue driver) to avoid layering violations in client
drivers (such as applespi).
Add an explicit DMI match table for MacBook8,1 and a module parameter
spi_pxa2xx_force_pio to allow forcing PIO mode on demand.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=108331
Signed-off-by: Shih-Yuan Lee <fourdollars@debian.org>
---
drivers/spi/spi-pxa2xx-pci.c | 35 +++++++++++++++++++++++++++++++++--
1 file changed, 33 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-pxa2xx-pci.c b/drivers/spi/spi-pxa2xx-pci.c
index cae77ac18520..31bdaa096d9e 100644
--- a/drivers/spi/spi-pxa2xx-pci.c
+++ b/drivers/spi/spi-pxa2xx-pci.c
@@ -18,9 +18,14 @@
#include <linux/dmaengine.h>
#include <linux/platform_data/dma-dw.h>
+#include <linux/dmi.h>
#include "spi-pxa2xx.h"
+static bool spi_pxa2xx_force_pio;
+module_param_named(force_pio, spi_pxa2xx_force_pio, bool, 0444);
+MODULE_PARM_DESC(force_pio, "Force PIO mode (disables DMA) for SPI transfers. ([0] = disabled, 1 = enabled)");
+
#define PCI_DEVICE_ID_INTEL_QUARK_X1000 0x0935
#define PCI_DEVICE_ID_INTEL_BYT 0x0f0e
#define PCI_DEVICE_ID_INTEL_MRFLD 0x1194
@@ -93,6 +98,32 @@ static void lpss_dma_put_device(void *dma_dev)
pci_dev_put(dma_dev);
}
+static const struct dmi_system_id pxa2xx_spi_pci_dmi_table[] = {
+ {
+ .ident = "Apple MacBook8,1",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Apple Inc."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "MacBook8,1"),
+ },
+ },
+ { }
+};
+
+static bool pxa2xx_spi_pci_can_dma(struct pci_dev *dev)
+{
+ if (spi_pxa2xx_force_pio) {
+ pci_info(dev, "Forcing PIO mode (disabling DMA)\n");
+ return false;
+ }
+
+ if (dmi_check_system(pxa2xx_spi_pci_dmi_table)) {
+ pci_info(dev, "MacBook8,1 detected: disabling DMA to force PIO mode\n");
+ return false;
+ }
+
+ return true;
+}
+
static int lpss_spi_setup(struct pci_dev *dev, struct pxa2xx_spi_controller *c)
{
struct ssp_device *ssp = &c->ssp;
@@ -166,7 +197,7 @@ static int lpss_spi_setup(struct pci_dev *dev, struct pxa2xx_spi_controller *c)
c->dma_filter = lpss_dma_filter;
c->dma_burst_size = 1;
- c->enable_dma = 1;
+ c->enable_dma = pxa2xx_spi_pci_can_dma(dev);
return 0;
}
@@ -238,7 +269,7 @@ static int mrfld_spi_setup(struct pci_dev *dev, struct pxa2xx_spi_controller *c)
c->dma_filter = lpss_dma_filter;
c->dma_burst_size = 8;
- c->enable_dma = 1;
+ c->enable_dma = pxa2xx_spi_pci_can_dma(dev);
return 0;
}
--
2.39.5
^ permalink raw reply related [flat|nested] 6+ messages in thread
* [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode
2026-07-18 16:06 [PATCH v14 0/3] spi: pxa2xx: MacBook8,1 quirk, runtime PM, and LPSS S3 resume state fixes Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1 Shih-Yuan Lee
@ 2026-07-18 16:07 ` Shih-Yuan Lee
2026-07-18 20:14 ` Mark Brown
2026-07-18 16:07 ` [PATCH v14 3/3] spi: pxa2xx: restore LPSS private register state on S3 resume Shih-Yuan Lee
2 siblings, 1 reply; 6+ messages in thread
From: Shih-Yuan Lee @ 2026-07-18 16:07 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-spi, linux-kernel, Shih-Yuan Lee
When operating in PIO mode on Intel LPSS SPI controllers, runtime PM
autosuspend clock-gates the hardware block, causing PCIe Completion
Timeouts on subsequent MMIO accesses.
To fix this:
- Scope PIO mode autosuspend lockout (pm_runtime_get_noresume() /
put_sync()) strictly to LPSS controllers via is_lpss_ssp(), preserving
autosuspend for non-LPSS SoCs.
- Acquire pm_runtime_get_noresume() exactly once in pxa2xx_spi_probe()
after spi_register_controller() succeeds, and release it via
pm_runtime_put_sync() in pxa2xx_spi_remove(). Using pm_runtime_put_sync()
ensures the runtime PM state machine transitions to RPM_SUSPENDED upon
driver unbind, preventing active child count leaks on the parent LPSS
power domain.
- Track clock state using drv_data->clk_enabled in helper functions
pxa2xx_spi_clk_enable/disable() to prevent clock count underflows
on error paths.
- Protect ssp_int() using drv_data->clk_enabled and drv_data->suspended
flags to return IRQ_NONE immediately if the device is suspended or
unclocked, avoiding unclocked MMIO reads and level-triggered shared IRQ
storms. Active SPI transfers hold a PM reference via the SPI core,
preventing autosuspend during FIFO transfers.
- Register IRQ in probe only after enabling the clock and clearing
suspended.
- Overhaul teardown sequence in pxa2xx_spi_remove(), suspend, and
runtime_suspend: first disable SSP hardware IRQ generation via
pxa_ssp_disable(), set suspended flag, synchronize IRQ to drain in-flight
handlers, and then disable clocks.
- Guard MMIO access in pxa2xx_spi_runtime_suspend() with
drv_data->clk_enabled check.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=108331
Signed-off-by: Shih-Yuan Lee <fourdollars@debian.org>
---
drivers/spi/spi-pxa2xx.c | 138 +++++++++++++++++++++++++++++----------
drivers/spi/spi-pxa2xx.h | 3 +
2 files changed, 108 insertions(+), 33 deletions(-)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index 6291d7c2e06f..443800bffbeb 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drivers/spi/spi-pxa2xx.c
@@ -72,7 +72,12 @@ struct chip_data {
#define LPSS_CAPS_CS_EN_SHIFT 9
#define LPSS_CAPS_CS_EN_MASK (0xf << LPSS_CAPS_CS_EN_SHIFT)
-#define LPSS_PRIV_CLOCK_GATE 0x38
+/* Offsets from drv_data->lpss_base */
+#define LPSS_PRIV_RESETS 0x04
+#define LPSS_PRIV_RESETS_IDMA BIT(2)
+#define LPSS_PRIV_RESETS_FUNC 0x3
+
+#define LPSS_PRIV_CLOCK_GATE 0x38
#define LPSS_PRIV_CLOCK_GATE_CLK_CTL_MASK 0x3
#define LPSS_PRIV_CLOCK_GATE_CLK_CTL_FORCE_ON 0x3
#define LPSS_PRIV_CLOCK_GATE_CLK_CTL_FORCE_OFF 0x0
@@ -713,6 +718,28 @@ static void handle_bad_msg(struct driver_data *drv_data)
dev_err(drv_data->ssp->dev, "bad message state in interrupt handler\n");
}
+static int pxa2xx_spi_clk_enable(struct driver_data *drv_data)
+{
+ int status;
+
+ if (drv_data->clk_enabled)
+ return 0;
+
+ status = clk_prepare_enable(drv_data->ssp->clk);
+ if (status == 0)
+ drv_data->clk_enabled = true;
+
+ return status;
+}
+
+static void pxa2xx_spi_clk_disable(struct driver_data *drv_data)
+{
+ if (drv_data->clk_enabled) {
+ clk_disable_unprepare(drv_data->ssp->clk);
+ drv_data->clk_enabled = false;
+ }
+}
+
static irqreturn_t ssp_int(int irq, void *dev_id)
{
struct driver_data *drv_data = dev_id;
@@ -721,19 +748,18 @@ static irqreturn_t ssp_int(int irq, void *dev_id)
u32 status;
/*
- * The IRQ might be shared with other peripherals so we must first
- * check that are we RPM suspended or not. If we are we assume that
- * the IRQ was not for us (we shouldn't be RPM suspended when the
- * interrupt is enabled).
+ * The IRQ might be shared with other peripherals or trigger during
+ * power state transitions. First check if device is suspended or if
+ * clock is disabled; if so, return IRQ_NONE immediately to avoid
+ * unclocked MMIO reads.
*/
- if (pm_runtime_suspended(drv_data->ssp->dev))
+ if (drv_data->suspended || !drv_data->clk_enabled)
return IRQ_NONE;
/*
- * If the device is not yet in RPM suspended state and we get an
- * interrupt that is meant for another device, check if status bits
- * are all set to one. That means that the device is already
- * powered off.
+ * If the device is not yet suspended and we get an interrupt that is
+ * meant for another device, check if status bits are all set to one.
+ * That means that the device is already powered off.
*/
status = pxa2xx_spi_read(drv_data, SSSR);
if (status == ~0)
@@ -1288,6 +1314,7 @@ int pxa2xx_spi_probe(struct device *dev, struct ssp_device *ssp,
drv_data->controller = controller;
drv_data->controller_info = platform_info;
drv_data->ssp = ssp;
+ drv_data->suspended = true; /* Start suspended until clock is enabled */
/* The spi->mode bits understood by this driver: */
controller->mode_bits = SPI_CPOL | SPI_CPHA | SPI_CS_HIGH | SPI_LOOP;
@@ -1330,10 +1357,6 @@ int pxa2xx_spi_probe(struct device *dev, struct ssp_device *ssp,
| SSSR_ROR | SSSR_TUR;
}
- status = request_irq(ssp->irq, ssp_int, IRQF_SHARED, dev_name(dev),
- drv_data);
- if (status < 0)
- return dev_err_probe(dev, status, "cannot get IRQ %d\n", ssp->irq);
/* Setup DMA if requested */
if (platform_info->enable_dma) {
@@ -1352,9 +1375,18 @@ int pxa2xx_spi_probe(struct device *dev, struct ssp_device *ssp,
}
/* Enable SOC clock */
- status = clk_prepare_enable(ssp->clk);
+ status = pxa2xx_spi_clk_enable(drv_data);
if (status)
- goto out_error_dma_irq_alloc;
+ goto out_error_dma_alloc;
+
+ drv_data->suspended = false;
+
+ status = request_irq(ssp->irq, ssp_int, IRQF_SHARED, dev_name(dev),
+ drv_data);
+ if (status < 0) {
+ status = dev_err_probe(dev, status, "cannot get IRQ %d\n", ssp->irq);
+ goto out_error_clock_enabled;
+ }
controller->max_speed_hz = clk_get_rate(ssp->clk);
/*
@@ -1434,7 +1466,7 @@ int pxa2xx_spi_probe(struct device *dev, struct ssp_device *ssp,
"ready", GPIOD_OUT_LOW);
if (IS_ERR(drv_data->gpiod_ready)) {
status = PTR_ERR(drv_data->gpiod_ready);
- goto out_error_clock_enabled;
+ goto out_error_irq_alloc;
}
}
@@ -1443,17 +1475,22 @@ int pxa2xx_spi_probe(struct device *dev, struct ssp_device *ssp,
status = spi_register_controller(controller);
if (status) {
dev_err_probe(dev, status, "problem registering SPI controller\n");
- goto out_error_clock_enabled;
+ goto out_error_irq_alloc;
}
+ if (is_lpss_ssp(drv_data) && !platform_info->enable_dma)
+ pm_runtime_get_noresume(dev);
+
return status;
+out_error_irq_alloc:
+ free_irq(ssp->irq, drv_data);
+
out_error_clock_enabled:
- clk_disable_unprepare(ssp->clk);
+ pxa2xx_spi_clk_disable(drv_data);
-out_error_dma_irq_alloc:
+out_error_dma_alloc:
pxa2xx_spi_dma_release(drv_data);
- free_irq(ssp->irq, drv_data);
return status;
}
@@ -1466,16 +1503,26 @@ void pxa2xx_spi_remove(struct device *dev)
spi_unregister_controller(drv_data->controller);
- /* Disable the SSP at the peripheral and SOC level */
+ /* Disable SSP interrupt generation on hardware level while clock is active */
pxa_ssp_disable(ssp);
- clk_disable_unprepare(ssp->clk);
- /* Release DMA */
- if (drv_data->controller_info->enable_dma)
- pxa2xx_spi_dma_release(drv_data);
+ /* Mark as suspended to prevent further IRQ handling */
+ drv_data->suspended = true;
+
+ /* Wait for any pending interrupt handlers to complete */
+ synchronize_irq(ssp->irq);
/* Release IRQ */
free_irq(ssp->irq, drv_data);
+
+ /* Safe to disable the SSP clock now */
+ pxa2xx_spi_clk_disable(drv_data);
+
+ /* Release DMA */
+ if (drv_data->controller_info->enable_dma)
+ pxa2xx_spi_dma_release(drv_data);
+ else if (is_lpss_ssp(drv_data))
+ pm_runtime_put_sync(dev);
}
EXPORT_SYMBOL_NS_GPL(pxa2xx_spi_remove, "SPI_PXA2xx");
@@ -1490,10 +1537,10 @@ static int pxa2xx_spi_suspend(struct device *dev)
return status;
pxa_ssp_disable(ssp);
+ drv_data->suspended = true;
+ synchronize_irq(ssp->irq);
- if (!pm_runtime_suspended(dev))
- clk_disable_unprepare(ssp->clk);
-
+ pxa2xx_spi_clk_disable(drv_data);
return 0;
}
@@ -1505,28 +1552,53 @@ static int pxa2xx_spi_resume(struct device *dev)
/* Enable the SSP clock */
if (!pm_runtime_suspended(dev)) {
- status = clk_prepare_enable(ssp->clk);
+ status = pxa2xx_spi_clk_enable(drv_data);
if (status)
return status;
}
+ if (is_lpss_ssp(drv_data))
+ lpss_ssp_setup(drv_data);
+
+ drv_data->suspended = false;
+
/* Start the queue running */
- return spi_controller_resume(drv_data->controller);
+ status = spi_controller_resume(drv_data->controller);
+ if (status) {
+ drv_data->suspended = true;
+ synchronize_irq(ssp->irq);
+ pxa2xx_spi_clk_disable(drv_data);
+ return status;
+ }
+
+ return 0;
}
static int pxa2xx_spi_runtime_suspend(struct device *dev)
{
struct driver_data *drv_data = dev_get_drvdata(dev);
- clk_disable_unprepare(drv_data->ssp->clk);
+ if (!drv_data->clk_enabled)
+ return 0;
+
+ pxa_ssp_disable(drv_data->ssp);
+ drv_data->suspended = true;
+ synchronize_irq(drv_data->ssp->irq);
+ pxa2xx_spi_clk_disable(drv_data);
return 0;
}
static int pxa2xx_spi_runtime_resume(struct device *dev)
{
struct driver_data *drv_data = dev_get_drvdata(dev);
+ int status;
+
+ status = pxa2xx_spi_clk_enable(drv_data);
+ if (status)
+ return status;
- return clk_prepare_enable(drv_data->ssp->clk);
+ drv_data->suspended = false;
+ return 0;
}
EXPORT_NS_GPL_DEV_PM_OPS(pxa2xx_spi_pm_ops, SPI_PXA2xx) = {
diff --git a/drivers/spi/spi-pxa2xx.h b/drivers/spi/spi-pxa2xx.h
index 447be0369384..44f37bf9c519 100644
--- a/drivers/spi/spi-pxa2xx.h
+++ b/drivers/spi/spi-pxa2xx.h
@@ -72,6 +72,9 @@ struct driver_data {
void __iomem *lpss_base;
+ bool suspended;
+ bool clk_enabled;
+
/* Optional slave FIFO ready signal */
struct gpio_desc *gpiod_ready;
};
--
2.39.5
^ permalink raw reply related [flat|nested] 6+ messages in thread
* [PATCH v14 3/3] spi: pxa2xx: restore LPSS private register state on S3 resume
2026-07-18 16:06 [PATCH v14 0/3] spi: pxa2xx: MacBook8,1 quirk, runtime PM, and LPSS S3 resume state fixes Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1 Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode Shih-Yuan Lee
@ 2026-07-18 16:07 ` Shih-Yuan Lee
2 siblings, 0 replies; 6+ messages in thread
From: Shih-Yuan Lee @ 2026-07-18 16:07 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-spi, linux-kernel, Shih-Yuan Lee
Intel LPSS SPI controllers lose all private register state across S3
suspend because the LPSS power domain is fully removed. On resume the
driver only re-enables the SSP clock, leaving the LPSS private registers
in their power-on-reset state, which causes two problems:
1. LPSS_PRIV_RESETS (offset 0x04 within the LPSS private space) stays
zero, keeping the functional block in reset. Any MMIO access while
the block is held in reset causes a PCIe Completion Timeout and a
watchdog-triggered system reset. LPSS_PRIV_RESETS_FUNC and
LPSS_PRIV_RESETS_IDMA must be de-asserted before any other register
access on resume.
2. The LPSS software chip-select control register must not be blindly
restored from its suspend-time snapshot: if CS was asserted at the
moment of suspend, restoring that state corrupts the first
post-resume SPI transaction. Instead, call lpss_ssp_setup() which
unconditionally writes SW_MODE | CS_HIGH (idle/deasserted), matching
the state established at probe time.
To resolve these issues safely:
- Wrap S3 suspend/resume with pm_runtime_resume_and_get() and
pm_runtime_put_autosuspend() to guarantee active clocks during MMIO
access and preserve PM reference counting.
- Restrict LPSS private register save/restore to LPT, BYT, and BSW
platforms via pxa2xx_spi_need_lpss_restore() (newer platforms are
handled by intel-lpss.c).
- Save only the first 6 LPSS private registers (offsets 0x00..0x14) in
drv_data during suspend, avoiding reserved offsets beyond 0x14.
- On resume, de-assert resets first, restore saved registers, call
lpss_ssp_setup(), and clear drv_data->suspended to prevent unclocked
IRQ access.
- Add error recovery paths for spi_controller_suspend/resume failures.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=108331
Signed-off-by: Shih-Yuan Lee <fourdollars@debian.org>
---
drivers/spi/spi-pxa2xx.c | 94 +++++++++++++++++++++++++++++++++++++---
drivers/spi/spi-pxa2xx.h | 1 +
2 files changed, 89 insertions(+), 6 deletions(-)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
index 443800bffbeb..864b9ca61bb2 100644
--- a/drivers/spi/spi-pxa2xx.c
+++ b/drivers/spi/spi-pxa2xx.c
@@ -194,6 +194,18 @@ static bool is_lpss_ssp(const struct driver_data *drv_data)
}
}
+static bool pxa2xx_spi_need_lpss_restore(const struct driver_data *drv_data)
+{
+ switch (drv_data->ssp_type) {
+ case LPSS_LPT_SSP:
+ case LPSS_BYT_SSP:
+ case LPSS_BSW_SSP:
+ return true;
+ default:
+ return false;
+ }
+}
+
static bool is_quark_x1000_ssp(const struct driver_data *drv_data)
{
return drv_data->ssp_type == QUARK_X1000_SSP;
@@ -1532,16 +1544,46 @@ static int pxa2xx_spi_suspend(struct device *dev)
struct ssp_device *ssp = drv_data->ssp;
int status;
- status = spi_controller_suspend(drv_data->controller);
- if (status)
+ status = pm_runtime_resume_and_get(dev);
+ if (status < 0)
return status;
+ status = spi_controller_suspend(drv_data->controller);
+ if (status) {
+ spi_controller_resume(drv_data->controller);
+ goto out_put;
+ }
+
+ /* Disable SSP interrupt generation on hardware level while clock is active */
pxa_ssp_disable(ssp);
+
+ /* Mark as suspended and synchronize IRQ before disabling clock */
drv_data->suspended = true;
synchronize_irq(ssp->irq);
+ if (pxa2xx_spi_need_lpss_restore(drv_data)) {
+ unsigned int i;
+
+ /*
+ * Save the first 6 LPSS private registers (offsets 0x00 to 0x14)
+ * while the clock is still enabled. They are lost when the LPSS
+ * power domain is removed across S3 and must be restored on resume.
+ * Use drv_data->lpss_base so the correct per-platform offset
+ * is applied regardless of LPSS IP revision.
+ * Registers beyond 0x14 (except CS control at 0x18) are reserved
+ * or unimplemented on LPT, and accessing them triggers a PCIe
+ * Completion Timeout causing a system halt.
+ */
+ for (i = 0; i < 6; i++)
+ drv_data->lpss_priv_ctx[i] = readl(drv_data->lpss_base + i * 4);
+ }
+
pxa2xx_spi_clk_disable(drv_data);
return 0;
+
+out_put:
+ pm_runtime_put_noidle(dev);
+ return status;
}
static int pxa2xx_spi_resume(struct device *dev)
@@ -1554,12 +1596,47 @@ static int pxa2xx_spi_resume(struct device *dev)
if (!pm_runtime_suspended(dev)) {
status = pxa2xx_spi_clk_enable(drv_data);
if (status)
- return status;
+ goto out_put;
}
- if (is_lpss_ssp(drv_data))
+ if (pxa2xx_spi_need_lpss_restore(drv_data)) {
+ unsigned int i;
+
+ /*
+ * The LPSS power domain is removed across S3, taking
+ * all private registers with it. De-assert the
+ * functional block and IDMA resets first; any MMIO
+ * access while the block is held in reset causes a
+ * PCIe Completion Timeout and a watchdog-triggered
+ * system reset.
+ */
+ writel(LPSS_PRIV_RESETS_FUNC | LPSS_PRIV_RESETS_IDMA,
+ drv_data->lpss_base + LPSS_PRIV_RESETS);
+
+ /* Restore the other 5 saved private registers */
+ for (i = 0; i < 6; i++) {
+ if (i == LPSS_PRIV_RESETS / 4)
+ continue;
+ writel(drv_data->lpss_priv_ctx[i],
+ drv_data->lpss_base + i * 4);
+ }
+ }
+
+ if (is_lpss_ssp(drv_data)) {
+ /*
+ * Re-initialise the SW chip-select control register so
+ * CS starts deasserted (SW_MODE | CS_HIGH), regardless
+ * of the state it was in at suspend time. A stale
+ * asserted CS on the first post-resume transaction
+ * corrupts the write-status response from the device.
+ */
lpss_ssp_setup(drv_data);
+ }
+ /*
+ * Now that resets are de-asserted and registers are restored,
+ * it is safe to handle interrupts.
+ */
drv_data->suspended = false;
/* Start the queue running */
@@ -1568,10 +1645,15 @@ static int pxa2xx_spi_resume(struct device *dev)
drv_data->suspended = true;
synchronize_irq(ssp->irq);
pxa2xx_spi_clk_disable(drv_data);
- return status;
+ goto out_put;
}
- return 0;
+out_put:
+ /* Let runtime PM autosuspend again if needed */
+ pm_runtime_mark_last_busy(dev);
+ pm_runtime_put_autosuspend(dev);
+
+ return status;
}
static int pxa2xx_spi_runtime_suspend(struct device *dev)
diff --git a/drivers/spi/spi-pxa2xx.h b/drivers/spi/spi-pxa2xx.h
index 44f37bf9c519..48169494f74e 100644
--- a/drivers/spi/spi-pxa2xx.h
+++ b/drivers/spi/spi-pxa2xx.h
@@ -71,6 +71,7 @@ struct driver_data {
irqreturn_t (*transfer_handler)(struct driver_data *drv_data);
void __iomem *lpss_base;
+ u32 lpss_priv_ctx[6];
bool suspended;
bool clk_enabled;
--
2.39.5
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1
2026-07-18 16:07 ` [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1 Shih-Yuan Lee
@ 2026-07-18 20:01 ` Mark Brown
0 siblings, 0 replies; 6+ messages in thread
From: Mark Brown @ 2026-07-18 20:01 UTC (permalink / raw)
To: Shih-Yuan Lee; +Cc: linux-spi, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Sun, Jul 19, 2026 at 12:07:00AM +0800, Shih-Yuan Lee wrote:
> Move the forced PIO mode DMI quirk to spi-pxa2xx-pci.c (the LPSS host
> controller PCI glue driver) to avoid layering violations in client
> drivers (such as applespi).
> Add an explicit DMI match table for MacBook8,1 and a module parameter
> spi_pxa2xx_force_pio to allow forcing PIO mode on demand.
Note that this will mean that the runtime PM bugs fixed in patch 2 are
exposed, breaking bisection on the affected platform. The actual change
looks fine.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode
2026-07-18 16:07 ` [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode Shih-Yuan Lee
@ 2026-07-18 20:14 ` Mark Brown
0 siblings, 0 replies; 6+ messages in thread
From: Mark Brown @ 2026-07-18 20:14 UTC (permalink / raw)
To: Shih-Yuan Lee; +Cc: linux-spi, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 3782 bytes --]
On Sun, Jul 19, 2026 at 12:07:01AM +0800, Shih-Yuan Lee wrote:
> When operating in PIO mode on Intel LPSS SPI controllers, runtime PM
> autosuspend clock-gates the hardware block, causing PCIe Completion
> Timeouts on subsequent MMIO accesses.
>
> To fix this:
> - Scope PIO mode autosuspend lockout (pm_runtime_get_noresume() /
> put_sync()) strictly to LPSS controllers via is_lpss_ssp(), preserving
> autosuspend for non-LPSS SoCs.
> - Acquire pm_runtime_get_noresume() exactly once in pxa2xx_spi_probe()
> after spi_register_controller() succeeds, and release it via
> pm_runtime_put_sync() in pxa2xx_spi_remove(). Using pm_runtime_put_sync()
> ensures the runtime PM state machine transitions to RPM_SUSPENDED upon
> driver unbind, preventing active child count leaks on the parent LPSS
> power domain.
> - Track clock state using drv_data->clk_enabled in helper functions
> pxa2xx_spi_clk_enable/disable() to prevent clock count underflows
> on error paths.
> - Protect ssp_int() using drv_data->clk_enabled and drv_data->suspended
> flags to return IRQ_NONE immediately if the device is suspended or
> unclocked, avoiding unclocked MMIO reads and level-triggered shared IRQ
> storms. Active SPI transfers hold a PM reference via the SPI core,
> preventing autosuspend during FIFO transfers.
> - Register IRQ in probe only after enabling the clock and clearing
> suspended.
> - Overhaul teardown sequence in pxa2xx_spi_remove(), suspend, and
> runtime_suspend: first disable SSP hardware IRQ generation via
> pxa_ssp_disable(), set suspended flag, synchronize IRQ to drain in-flight
> handlers, and then disable clocks.
> - Guard MMIO access in pxa2xx_spi_runtime_suspend() with
> drv_data->clk_enabled check.
This is a very big change doing a lot of different things which could
probably use being split out, if you find yourself writing a list like
this it's often a sign that the bullet points should be split out (as
submitting-patches.rst hints at).
> +static int pxa2xx_spi_clk_enable(struct driver_data *drv_data)
> +{
> + int status;
> +
> + if (drv_data->clk_enabled)
> + return 0;
> +
> + status = clk_prepare_enable(drv_data->ssp->clk);
> + if (status == 0)
> + drv_data->clk_enabled = true;
> +
> + return status;
> +}
This sort of refcount suppression is often a bit worrying, why are we
doing things this way - the changelog mentions error paths but which
error paths, and why is this the most sensible fix?
Also we typically use 'ret' in the kernel.
> /*
> - * The IRQ might be shared with other peripherals so we must first
> - * check that are we RPM suspended or not. If we are we assume that
> - * the IRQ was not for us (we shouldn't be RPM suspended when the
> - * interrupt is enabled).
> + * The IRQ might be shared with other peripherals or trigger during
> + * power state transitions. First check if device is suspended or if
> + * clock is disabled; if so, return IRQ_NONE immediately to avoid
> + * unclocked MMIO reads.
> */
> - if (pm_runtime_suspended(drv_data->ssp->dev))
> + if (drv_data->suspended || !drv_data->clk_enabled)
> return IRQ_NONE;
Why are we switching to this suspended flag rather than using
pm_runtime_suspended()?
> static int pxa2xx_spi_runtime_suspend(struct device *dev)
> {
> struct driver_data *drv_data = dev_get_drvdata(dev);
>
> - clk_disable_unprepare(drv_data->ssp->clk);
> + if (!drv_data->clk_enabled)
> + return 0;
> +
> + pxa_ssp_disable(drv_data->ssp);
Note that there's an inconsistently quirk to suppress SSP disables on
MMP2, did you check if we need to do that here? It comes from
29d7e05c5f75 ("spi: pxa2xx: Avoid touching SSCR0_SSE on MMP2").
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2026-07-18 20:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-18 16:06 [PATCH v14 0/3] spi: pxa2xx: MacBook8,1 quirk, runtime PM, and LPSS S3 resume state fixes Shih-Yuan Lee
2026-07-18 16:07 ` [PATCH v14 1/3] spi: pxa2xx: disable DMA for Apple MacBook8,1 Shih-Yuan Lee
2026-07-18 20:01 ` Mark Brown
2026-07-18 16:07 ` [PATCH v14 2/3] spi: pxa2xx: fix runtime PM and interrupt handling in PIO mode Shih-Yuan Lee
2026-07-18 20:14 ` Mark Brown
2026-07-18 16:07 ` [PATCH v14 3/3] spi: pxa2xx: restore LPSS private register state on S3 resume Shih-Yuan Lee
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox