linux-kernel - Re: [PATCH] spi: spi-cadence-quadspi: Fix OSPI NOR failures during system resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172372876860.37632.10724090127376087246.b4-ty@kernel.org>
Date: Thu, 15 Aug 2024 14:32:48 +0100
From: Mark Brown <broonie@...nel.org>
To: Vignesh Raghavendra <vigneshr@...com>
Cc: theo.lebrun@...tlin.com, d-gole@...com, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] spi: spi-cadence-quadspi: Fix OSPI NOR failures during
 system resume

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