From: Jiale Yao <yaojiale02@163.com>
To: Mark Brown <broonie@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Felix Gu <ustc.gu@gmail.com>,
Atsushi Nemoto <atsushi.nemoto@sord.co.jp>,
linux-spi@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Jiale Yao <yaojiale02@163.com>
Subject: [PATCH 0/2] spi: handle runtime resume failures
Date: Mon, 19 Oct 2026 16:44:41 +0800 [thread overview]
Message-ID: <20261019084443.1824122-1-yaojiale02@163.com> (raw)
The STM32 OSPI remove path and the TI QSPI clock setup helper ignore
pm_runtime_resume_and_get() failures. A failed runtime resume leaves the
controller unavailable, so following register accesses are unsafe and a
later runtime PM put can be unmatched.
Keep OSPI resource teardown on a failed resume while skipping the
controller register write and its matching put. Return the error from the
QSPI clock setup helper and propagate it before either caller touches the
controller registers.
Jiale Yao (2):
spi: stm32-ospi: handle runtime resume failure in remove
spi: ti-qspi: handle setup clock runtime resume failure
drivers/spi/spi-stm32-ospi.c | 12 ++++++++----
drivers/spi/spi-ti-qspi.c | 21 ++++++++++++++++-----
2 files changed, 24 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2026-10-19 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 8:44 Jiale Yao [this message]
2026-10-19 8:44 ` [PATCH 1/2] spi: stm32-ospi: handle runtime resume failure in remove Jiale Yao
2026-10-30 14:47 ` Patrice CHOTARD
2026-10-19 8:44 ` [PATCH 2/2] spi: ti-qspi: handle setup clock runtime resume failure Jiale Yao
2026-10-19 23:57 ` Atsushi Nemoto
2026-11-02 22:39 ` [PATCH 0/2] spi: handle runtime resume failures Mark Brown
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=20261019084443.1824122-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=alexandre.torgue@foss.st.com \
--cc=atsushi.nemoto@sord.co.jp \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@foss.st.com \
--cc=ustc.gu@gmail.com \
/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
all inboxes | Powered by JetHome®