[PATCH 0/3] spi: atmel-quadspi: add runtime pm support

Claudiu Beznea posted 3 patches 3 years, 10 months ago
drivers/spi/atmel-quadspi.c | 104 ++++++++++++++++++++++++++++++++----
1 file changed, 93 insertions(+), 11 deletions(-)
[PATCH 0/3] spi: atmel-quadspi: add runtime pm support
Posted by Claudiu Beznea 3 years, 10 months ago
Hi,

The following series adds runtime PM support for atmel-quadspi driver.
clk_disable()/clk_enable() is called on proper
runtime_suspend()/runtime_resume() ops. Along with it 2 minor cleanups
were added (patches 2/3, 3/3).

Thank you,
Claudiu Beznea

Claudiu Beznea (3):
  spi: atmel-quadspi: add runtime pm support
  spi: atmel-quadspi: use pm_ptr()
  spi: atmel-quadspi: align condition to parenthesis

 drivers/spi/atmel-quadspi.c | 104 ++++++++++++++++++++++++++++++++----
 1 file changed, 93 insertions(+), 11 deletions(-)

-- 
2.34.1
Re: [PATCH 0/3] spi: atmel-quadspi: add runtime pm support
Posted by Mark Brown 3 years, 10 months ago
On Thu, 9 Jun 2022 11:42:43 +0300, Claudiu Beznea wrote:
> The following series adds runtime PM support for atmel-quadspi driver.
> clk_disable()/clk_enable() is called on proper
> runtime_suspend()/runtime_resume() ops. Along with it 2 minor cleanups
> were added (patches 2/3, 3/3).
> 
> Thank you,
> Claudiu Beznea
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: atmel-quadspi: add runtime pm support
      commit: c349fad389c5916facead610d454250f67cfb20b
[2/3] spi: atmel-quadspi: use pm_ptr()
      commit: f11ec1cc46e38f0feac3721a03c21fa99167e329
[3/3] spi: atmel-quadspi: align condition to parenthesis
      commit: af7c2d4145b57c15d25a092cfb5a91708c72b541

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