From: Joshua Crofts <crofts@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: omap-sham: remove redundant pm_runtime_dont_use_autosuspend() calls
Date: Sun, 8 Nov 2026 13:11:06 +0100 [thread overview]
Message-ID: <20261108131106.0fde6459@systembl0wer> (raw)
In-Reply-To: <20261107-crypto-dont-use-autosuspend-removal-v1-1-62696ad3ff0e@kernel.org>
On Sat, 07 Nov 2026 13:39:43 +0100
Joshua Crofts <crofts@kernel.org> wrote:
> Since commit d1706f9da9f4 ("PM: runtime: call pm_runtime_dont_use_autosuspend() on reinit()"),
> driver core is now responsible for undoing any
> pm_runtime_use_autosuspend() calls on driver exit.
>
> Remove the redundant function calls.
>
> Signed-off-by: Joshua Crofts <crofts@kernel.org>
> ---
> drivers/crypto/omap-sham.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
> index 5e739415a010..72182f190084 100644
> --- a/drivers/crypto/omap-sham.c
> +++ b/drivers/crypto/omap-sham.c
> @@ -2109,7 +2109,6 @@ static int omap_sham_probe(struct platform_device *pdev)
> list_del(&dd->list);
> spin_unlock_bh(&sham.lock);
> err_pm:
> - pm_runtime_dont_use_autosuspend(dev);
> pm_runtime_disable(dev);
> if (!dd->polling_mode)
> dma_release_channel(dd->dma_lch);
> @@ -2131,7 +2130,6 @@ static void omap_sham_remove(struct platform_device *pdev)
> omap_sham_unregister_algs(dd->pdata);
> crypto_engine_exit(dd->engine);
> cancel_work_sync(&dd->done_task);
> - pm_runtime_dont_use_autosuspend(&pdev->dev);
Okay, drop this patch for the time being - the dont_use_autosuspend() ensures
that the .runtime_suspend callback is executed.
Thanks.
--
Kind regards,
Joshua Crofts
prev parent reply other threads:[~2026-11-08 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 12:39 [PATCH] crypto: omap-sham: remove redundant pm_runtime_dont_use_autosuspend() calls Joshua Crofts
2026-11-07 12:56 ` sashiko-bot
2026-11-08 12:11 ` Joshua Crofts [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261108131106.0fde6459@systembl0wer \
--to=crofts@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.