From: Mark Brown <broonie@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: theo.lebrun@bootlin.com, d-gole@ti.com,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] spi: spi-cadence-quadspi: Fix OSPI NOR failures during system resume
Date: Thu, 15 Aug 2024 14:32:48 +0100 [thread overview]
Message-ID: <172372876860.37632.10724090127376087246.b4-ty@kernel.org> (raw)
In-Reply-To: <20240814151237.3856184-1-vigneshr@ti.com>
On Wed, 14 Aug 2024 20:42:37 +0530, Vignesh Raghavendra wrote:
> Its necessary to call pm_runtime_force_*() hooks as part of system
> suspend/resume calls so that the runtime_pm hooks get called. This
> ensures latest state of the IP is cached and restored during system
> sleep. This is especially true if runtime autosuspend is enabled as
> runtime suspend hooks may not be called at all before system sleeps.
>
> Without this patch, OSPI NOR enumeration (READ_ID) fails during resume
> as context saved during suspend path is inconsistent.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-cadence-quadspi: Fix OSPI NOR failures during system resume
commit: 57d5af2660e9443b081eeaf1c373b3ce48477828
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
prev parent reply other threads:[~2024-08-15 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 15:12 Vignesh Raghavendra
2024-08-14 17:25 ` Mark Brown
2024-08-15 13:32 ` Mark Brown [this message]
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=172372876860.37632.10724090127376087246.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=d-gole@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=theo.lebrun@bootlin.com \
--cc=vigneshr@ti.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®