From: Michal Simek <michal.simek@amd.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Michal Simek" <michal.simek@xilinx.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH] i2c: xiic: Make sure to disable clock on .remove()
Date: Thu, 1 Dec 2022 12:42:38 +0100 [thread overview]
Message-ID: <da91aa37-3807-a9c7-d072-7855f858adf5@amd.com> (raw)
In-Reply-To: <20221019202808.88779-1-u.kleine-koenig@pengutronix.de>
On 10/19/22 22:28, Uwe Kleine-König wrote:
>
> If for whatever reasons pm_runtime_resume_and_get() failed, .remove() is
> exited early, the clock isn't freed and runtime PM state isn't reset.
>
> The right thing to do however is to free all resources that don't need
> HW access after a problem with runtime PM. Also issue a warning in that
> case and return 0 to suppress a less helpful warning by the driver core.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> drivers/i2c/busses/i2c-xiic.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-xiic.c b/drivers/i2c/busses/i2c-xiic.c
> index b3fe6b2aa3ca..809d6eadae2d 100644
> --- a/drivers/i2c/busses/i2c-xiic.c
> +++ b/drivers/i2c/busses/i2c-xiic.c
> @@ -858,11 +858,14 @@ static int xiic_i2c_remove(struct platform_device *pdev)
> /* remove adapter & data */
> i2c_del_adapter(&i2c->adap);
>
> - ret = pm_runtime_resume_and_get(i2c->dev);
> + ret = pm_runtime_get_sync(i2c->dev);
> +
> if (ret < 0)
> - return ret;
> + dev_warn(&pdev->dev, "Failed to activate device for removal (%pe)\n",
> + ERR_PTR(ret));
> + else
> + xiic_deinit(i2c);
>
> - xiic_deinit(i2c);
> pm_runtime_put_sync(i2c->dev);
> clk_disable_unprepare(i2c->clk);
> pm_runtime_disable(&pdev->dev);
>
> base-commit: 9abf2313adc1ca1b6180c508c25f22f9395cc780
> --
> 2.37.2
>
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2022-12-01 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 20:28 [PATCH] i2c: xiic: Make sure to disable clock on .remove() Uwe Kleine-König
2022-12-01 11:42 ` Michal Simek [this message]
2022-12-07 20:05 ` Wolfram Sang
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=da91aa37-3807-a9c7-d072-7855f858adf5@amd.com \
--to=michal.simek@amd.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=u.kleine-koenig@pengutronix.de \
/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