From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 46/51] w1: omap-hdq: Switch to __pm_runtime_put_autosuspend()
Date: Fri, 4 Oct 2024 16:05:54 +0200 [thread overview]
Message-ID: <2232cb38-1396-4f0a-bc62-8ff4c02f8be7@kernel.org> (raw)
In-Reply-To: <20241004094145.114133-1-sakari.ailus@linux.intel.com>
On 04/10/2024 11:41, Sakari Ailus wrote:
> pm_runtime_put_autosuspend() will soon be changed to include a call to
> pm_runtime_mark_last_busy(). This patch switches the current users to
> __pm_runtime_put_autosuspend() which will continue to have the
> functionality of old pm_runtime_put_autosuspend().
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/w1/masters/omap_hdq.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/w1/masters/omap_hdq.c b/drivers/w1/masters/omap_hdq.c
> index d1cb5190445a..b7e87a3ef62d 100644
> --- a/drivers/w1/masters/omap_hdq.c
> +++ b/drivers/w1/masters/omap_hdq.c
> @@ -446,7 +446,7 @@ static u8 omap_w1_triplet(void *_hdq, u8 bdir)
> mutex_unlock(&hdq_data->hdq_mutex);
> rtn:
> pm_runtime_mark_last_busy(hdq_data->dev);
> - pm_runtime_put_autosuspend(hdq_data->dev);
> + __pm_runtime_put_autosuspend(hdq_data->dev);
So just make the switch by dropping pm_runtime_mark_last_busy(). This is
unnecessary churn.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-04 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:41 [PATCH 00/51] treewide: Switch to __pm_runtime_put_autosuspend() Sakari Ailus
2024-10-04 9:41 ` [PATCH 03/51] bus: sunxi-rsb: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 04/51] hwrng: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 14/51] HSI: omap_ssi_port: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 27/51] mei: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 26/51] mfd: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 35/51] power: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 46/51] w1: omap-hdq: " Sakari Ailus
2024-10-04 14:05 ` Krzysztof Kozlowski [this message]
2024-10-04 14:38 ` [PATCH 00/51] treewide: " Ulf Hansson
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:34 ` Ulf Hansson
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-08 20:38 ` Uwe Kleine-König
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=2232cb38-1396-4f0a-bc62-8ff4c02f8be7@kernel.org \
--to=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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