From: Derek Basehore <dbasehore@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: wsa@the-dreams.de, linux-i2c@vger.kernel.org,
dianders@chromium.org, dtor@chromium.org,
venkateswarlu.v.vinjamuri@intel.corp-partner.google.com,
Derek Basehore <dbasehore@chromium.org>
Subject: [PATCH] i2c: enable async suspend/resume on i2c devices
Date: Thu, 26 Jul 2018 15:55:08 -0700 [thread overview]
Message-ID: <20180726225508.74612-1-dbasehore@chromium.org> (raw)
This enables the async suspend property for i2c devices. This reduces
the suspend/resume time considerably on platforms with multiple i2c
devices (such as a trackpad or touchscreen).
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
---
drivers/i2c/i2c-core-base.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
index 1ba40bb2b966..3382bb7e1dcc 100644
--- a/drivers/i2c/i2c-core-base.c
+++ b/drivers/i2c/i2c-core-base.c
@@ -749,6 +749,7 @@ i2c_new_device(struct i2c_adapter *adap, struct i2c_board_info const *info)
client->dev.of_node = info->of_node;
client->dev.fwnode = info->fwnode;
+ device_enable_async_suspend(&client->dev);
i2c_dev_set_name(adap, client, info);
if (info->properties) {
--
2.18.0.345.g5c9ce644c3-goog
next reply other threads:[~2018-07-26 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 22:55 Derek Basehore [this message]
2018-07-27 10:44 ` [PATCH] i2c: enable async suspend/resume on i2c devices Andy Shevchenko
2018-07-27 12:07 ` Hans de Goede
2018-07-27 16:17 ` dbasehore .
2018-08-14 17:52 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2020-03-27 15:19 Ricardo Cañuelo
2020-03-27 15:43 ` Wolfram Sang
2020-03-27 20:26 ` dbasehore .
2020-03-29 10:24 ` Ricardo Cañuelo
2020-03-29 12:49 ` Ezequiel Garcia
2020-04-08 5:06 ` dbasehore .
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=20180726225508.74612-1-dbasehore@chromium.org \
--to=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkateswarlu.v.vinjamuri@intel.corp-partner.google.com \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).