From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: James Ogletree <jogletre@opensource.cirrus.com>,
Fred Treven <fred.treven@cirrus.com>,
Ben Bright <ben.bright@cirrus.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: patches@opensource.cirrus.com, linux-input@vger.kernel.org
Subject: [PATCH 21/51] Input: cs40l50: Switch to __pm_runtime_put_autosuspend()
Date: Fri, 4 Oct 2024 12:41:23 +0300 [thread overview]
Message-ID: <20241004094123.113708-1-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20241004094101.113349-1-sakari.ailus@linux.intel.com>
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/input/misc/cs40l50-vibra.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/input/misc/cs40l50-vibra.c b/drivers/input/misc/cs40l50-vibra.c
index 03bdb7c26ec0..8555f0d93d3f 100644
--- a/drivers/input/misc/cs40l50-vibra.c
+++ b/drivers/input/misc/cs40l50-vibra.c
@@ -307,7 +307,7 @@ static void cs40l50_add_worker(struct work_struct *work)
}
err_pm:
pm_runtime_mark_last_busy(vib->dev);
- pm_runtime_put_autosuspend(vib->dev);
+ __pm_runtime_put_autosuspend(vib->dev);
err_exit:
work_data->error = error;
}
@@ -366,7 +366,7 @@ static void cs40l50_start_worker(struct work_struct *work)
}
pm_runtime_mark_last_busy(vib->dev);
- pm_runtime_put_autosuspend(vib->dev);
+ __pm_runtime_put_autosuspend(vib->dev);
err_free:
kfree(work_data);
}
@@ -382,7 +382,7 @@ static void cs40l50_stop_worker(struct work_struct *work)
vib->dsp.write(vib->dev, vib->regmap, vib->dsp.stop_cmd);
pm_runtime_mark_last_busy(vib->dev);
- pm_runtime_put_autosuspend(vib->dev);
+ __pm_runtime_put_autosuspend(vib->dev);
kfree(work_data);
}
@@ -454,7 +454,7 @@ static void cs40l50_erase_worker(struct work_struct *work)
kfree(erase_effect);
err_pm:
pm_runtime_mark_last_busy(vib->dev);
- pm_runtime_put_autosuspend(vib->dev);
+ __pm_runtime_put_autosuspend(vib->dev);
err_exit:
work_data->error = error;
}
--
2.39.5
next prev parent reply other threads:[~2024-10-04 9:41 UTC|newest]
Thread overview: 19+ 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 ` Sakari Ailus [this message]
2024-10-04 11:09 ` [PATCH 21/51] Input: cs40l50: " Dmitry Torokhov
2024-10-04 9:41 ` [PATCH 20/51] Input: omap4-keypad: " Sakari Ailus
2024-10-04 9:55 ` Andreas Kemnade
2024-10-04 10:26 ` Sakari Ailus
2024-10-04 10:54 ` Andreas Kemnade
2024-10-04 11:08 ` Dmitry Torokhov
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=20241004094123.113708-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ben.bright@cirrus.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fred.treven@cirrus.com \
--cc=jogletre@opensource.cirrus.com \
--cc=linux-input@vger.kernel.org \
--cc=patches@opensource.cirrus.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).