Re: [PATCH v2 6/6] memory: renesas-rpc-if: Use runtime PM autosuspend after transfers

[Wolfram Sang <wsa+renesas@sang-engineering.com>]

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

On Mon, Jul 27, 2026 at 11:34:49AM +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> 
> Replace pm_runtime_put() with pm_runtime_put_autosuspend() after manual
> transfers and direct memory-mapped read/write operations.
> 
> Flash page programming may be performed as a sequence of closely spaced
> transfer operations. Calling pm_runtime_put() after each operation allows
> the runtime PM core to suspend the controller between successive
> transfers, introducing unnecessary suspend/resume cycles and potentially
> interrupting multi-step transfer sequences.
> 
> Use pm_runtime_put_autosuspend() instead so the controller remains
> active while transfers continue, allowing it to suspend only after an
> idle period.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>

I tested this series with my SparrowHawk but it doesn't use the xSPI
code paths, so only this patch is only affected. No improvements, but
neither regressions.

Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

> Note corresponding pm_runtime_set_autosuspend_delay()/pm_runtime_use_autosuspend()
> calls are already present in SPI driver.

Unless I am missing it, there is no pm_runtime_set_autosuspend_delay()
in the driver nor in this patchset?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]