OSPI pm_runtime fixes

[PATCH 0/2] OSPI pm_runtime fixes

Posted by Anurag Dutta 3 months ago

Hi all
This short series introduces fixes for OSPI pm_runtime to balance the
runtime PM reference counting.

Logs :
https://gist.github.com/anuragdutta731/238dbc6d9ff7927c63cd4dcfc51dfa97

Anurag Dutta (2):
  spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance
  spi: spi-cadence-quadspi: Remove duplicate
    pm_runtime_put_autosuspend() call

 drivers/spi/spi-cadence-quadspi.c | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

-- 
2.34.1

Re: [PATCH 0/2] OSPI pm_runtime fixes

Posted by Mark Brown 2 months, 3 weeks ago

On Wed, 05 Nov 2025 21:41:44 +0530, Anurag Dutta wrote:
> This short series introduces fixes for OSPI pm_runtime to balance the
> runtime PM reference counting.
> 
> Logs :
> https://gist.github.com/anuragdutta731/238dbc6d9ff7927c63cd4dcfc51dfa97
> 
> Anurag Dutta (2):
>   spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance
>   spi: spi-cadence-quadspi: Remove duplicate
>     pm_runtime_put_autosuspend() call
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance
      commit: f1eb4e792bb1ee3dcdffa66f8a83a4867cda2dd3
[2/2] spi: spi-cadence-quadspi: Remove duplicate pm_runtime_put_autosuspend() call
      commit: 10eaa4c4a257944e9b30d13fda7d09164a70866d

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