mbox series

[0/2] Fix PM Hooks in the Cadence Quad SPI Driver

Message ID 20230417091027.966146-1-d-gole@ti.com (mailing list archive)
Headers show
Series Fix PM Hooks in the Cadence Quad SPI Driver | expand

Message

Dhruva Gole April 17, 2023, 9:10 a.m. UTC 
This series adds fixes to the Suspend and Resume Hooks of the CQSPI Driver.
Earlier, the ltp-ddt test "OSPI_S_FUNC_DD_RW_ERASESIZE_UBIFS" failed
post system suspend resume. It is now passing as shown in [0].

Tested on top of linux-next (next-20230414) on an AM625-SK-EVM. For logs,
please refer [0].

[0] https://gist.github.com/DhruvaG2000/29b15f9c8a1e632c6819a986e5f28ab2

Dhruva Gole (2):
  spi: cadence-quadspi: use macro SIMPLE_DEV_PM_OPS
  spi: cadence-quadspi: fix suspend-resume implementations

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

Comments

Mark Brown April 18, 2023, 4:21 p.m. UTC | #1 
On Mon, 17 Apr 2023 14:40:25 +0530, Dhruva Gole wrote:
> This series adds fixes to the Suspend and Resume Hooks of the CQSPI Driver.
> Earlier, the ltp-ddt test "OSPI_S_FUNC_DD_RW_ERASESIZE_UBIFS" failed
> post system suspend resume. It is now passing as shown in [0].
> 
> Tested on top of linux-next (next-20230414) on an AM625-SK-EVM. For logs,
> please refer [0].
> 
> [...]

Applied to

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

Thanks!

[2/2] spi: cadence-quadspi: fix suspend-resume implementations
      commit: 2087e85bb66ee3652dafe732bb9b9b896229eafc

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