From: Felipe Balbi <balbi@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Joel Fernandes <joelf@ti.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, Joachim Eastwood <manabian@gmail.com>
Subject: Re: [PATCH] crypto: omap-des - handle error of pm_runtime_get_sync
Date: Tue, 15 Apr 2014 10:50:31 -0500 [thread overview]
Message-ID: <20140415155031.GA14623@saruman.home> (raw)
In-Reply-To: <1397575982-24866-1-git-send-email-nm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Hi,
On Tue, Apr 15, 2014 at 10:33:02AM -0500, Nishanth Menon wrote:
> pm_runtime_get_sync may not always succeed depending on SoC involved. So
> handle the error appropriately.
>
> Reported-by: Joachim Eastwood <manabian@gmail.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
>
> based on v3.15-rc1
>
> Report-thread: http://marc.info/?t=139750330400002&r=1&w=2
>
> omap2plus_defconfig + CONFIG_CRYPTO_DEV_OMAP_DES=y
>
> pandaboard-es-before: http://slexy.org/raw/s21rGPFnKl
> pandaboard-es-after: http://slexy.org/raw/s2A4UFQVna
>
> drivers/crypto/omap-des.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/omap-des.c b/drivers/crypto/omap-des.c
> index ec5f131..c2d362f 100644
> --- a/drivers/crypto/omap-des.c
> +++ b/drivers/crypto/omap-des.c
> @@ -223,12 +223,18 @@ static void omap_des_write_n(struct omap_des_dev *dd, u32 offset,
>
> static int omap_des_hw_init(struct omap_des_dev *dd)
> {
> + int err;
> +
> /*
> * clocks are enabled when request starts and disabled when finished.
> * It may be long delays between requests.
> * Device might go to off mode to save power.
> */
> - pm_runtime_get_sync(dd->dev);
> + err = pm_runtime_get_sync(dd->dev);
> + if (err < 0) {
> + dev_err(dd->dev, "failed to get_sync(%d)\n", err);
> + return err;
even when get() fails, you must put().
> + }
>
> if (!(dd->flags & FLAGS_INIT)) {
> dd->flags |= FLAGS_INIT;
> @@ -1083,7 +1089,11 @@ static int omap_des_probe(struct platform_device *pdev)
> dd->phys_base = res->start;
>
> pm_runtime_enable(dev);
> - pm_runtime_get_sync(dev);
> + err = pm_runtime_get_sync(dev);
> + if (err < 0) {
> + dev_err(dd->dev, "failed to get_sync(%d)\n", err);
> + goto err_get;
this leaves usage_count incremented, needs a put() here too.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-15 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 15:33 [PATCH] crypto: omap-des - handle error of pm_runtime_get_sync Nishanth Menon
2014-04-15 15:50 ` Felipe Balbi [this message]
2014-04-15 16:44 ` Nishanth Menon
2014-04-15 16:58 ` [PATCH V2] " Nishanth Menon
2014-04-15 17:05 ` Felipe Balbi
2014-04-15 17:06 ` Joachim Eastwood
2014-04-15 17:18 ` Nishanth Menon
2014-04-15 17:51 ` Joel Fernandes
2014-04-16 13:50 ` Herbert Xu
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=20140415155031.GA14623@saruman.home \
--to=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=joelf@ti.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=nm@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).