From: Fabio Estevam <festevam@gmail.com>
To: herbert@gondor.apana.org.au
Cc: horia.geanta@nxp.com, pankaj.gupta@nxp.com,
sahil.malhotra@nxp.com, gaurav.jain@nxp.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Fabio Estevam <festevam@nabladev.com>,
stable@vger.kernel.org
Subject: [PATCH] crypto: caam: jr: Use dedicated shutdown callback
Date: Wed, 28 Oct 2026 10:28:25 -0300 [thread overview]
Message-ID: <20261028132825.657546-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@nabladev.com>
The CAAM job ring platform driver uses caam_jr_remove() as its
shutdown callback.
The remove path refuses to shut down a job ring while crypto
consumers still hold references to it. This is necessary during
driver unbinding, but causes the following warning on reboot:
caam_jr 30903000.jr: Device is busy; consumers might start to crash
Unlike driver removal, system shutdown does not require
unregistering crypto algorithms or releasing driver resources.
Introduce a dedicated platform shutdown callback that shuts down
the hardware job ring without checking consumer references.
Keep the reference checks and algorithm unregistration in the
remove path.
Tested on a i.MX8MP custom-board.
Cc: stable@vger.kernel.org
Fixes: c007e720989e ("crypto: caam/jr - add .shutdown hook")
Signed-off-by: Fabio Estevam <festevam@nabladev.com>
---
drivers/crypto/caam/jr.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/caam/jr.c b/drivers/crypto/caam/jr.c
index cf725a6ac0fb..75be668b74b8 100644
--- a/drivers/crypto/caam/jr.c
+++ b/drivers/crypto/caam/jr.c
@@ -178,6 +178,15 @@ static int caam_jr_shutdown(struct device *dev)
return ret;
}
+static void caam_jr_platform_shutdown(struct platform_device *pdev)
+{
+ int ret;
+
+ ret = caam_jr_shutdown(&pdev->dev);
+ if (ret)
+ dev_err(&pdev->dev, "Failed to shut down job ring: %d\n", ret);
+}
+
static void caam_jr_remove(struct platform_device *pdev)
{
int ret;
@@ -812,7 +821,7 @@ static struct platform_driver caam_jr_driver = {
},
.probe = caam_jr_probe,
.remove = caam_jr_remove,
- .shutdown = caam_jr_remove,
+ .shutdown = caam_jr_platform_shutdown,
};
static int __init jr_driver_init(void)
--
2.43.0
reply other threads:[~2026-10-28 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261028132825.657546-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.com \
--cc=sahil.malhotra@nxp.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox