mbox series

[0/2] spi: bcm63xx: fix pm_runtime

Message ID 20210223151851.4110-1-noltari@gmail.com (mailing list archive)
Headers show
Series spi: bcm63xx: fix pm_runtime | expand

Message

Álvaro Fernández Rojas Feb. 23, 2021, 3:18 p.m. UTC
Both BCM63xx SPI drivers enable auto_runtime_pm, but they don't call
pm_runtime_enable(), which results in "Failed to power device" when PM support
is enabled.

Álvaro Fernández Rojas (2):
  spi: bcm63xx-spi: fix pm_runtime
  spi: bcm63xx-hsspi: fix pm_runtime

 drivers/spi/spi-bcm63xx-hsspi.c | 7 ++++++-
 drivers/spi/spi-bcm63xx.c       | 6 +++++-
 2 files changed, 11 insertions(+), 2 deletions(-)

Comments

Mark Brown Feb. 24, 2021, 4:58 p.m. UTC | #1
On Tue, 23 Feb 2021 16:18:49 +0100, Álvaro Fernández Rojas wrote:
> Both BCM63xx SPI drivers enable auto_runtime_pm, but they don't call
> pm_runtime_enable(), which results in "Failed to power device" when PM support
> is enabled.
> 
> Álvaro Fernández Rojas (2):
>   spi: bcm63xx-spi: fix pm_runtime
>   spi: bcm63xx-hsspi: fix pm_runtime
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: bcm63xx-spi: fix pm_runtime
      commit: 73ae625da5c36300fccd809738e7c68f49ebce35
[2/2] spi: bcm63xx-hsspi: fix pm_runtime
      commit: 216e8e80057a9f0b6366327881acf88eaf9f1fd4

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