From: Sonny Rao <sonnyrao@chromium.org>
To: jic23@cam.ac.uk
Cc: linux-pm@lists.linux-foundation.org, bleung@chromium.org,
snanda@chromium.org, Sonny Rao <sonnyrao@chromium.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
Andrew Morton <akpm@linux-foundation.org>,
Phillip Kurtenbach <pkurtenbach@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Enable async suspend/resume on industrial IO devices
Date: Tue, 5 Apr 2011 19:45:14 -0700 [thread overview]
Message-ID: <1302057915-13549-1-git-send-email-sonnyrao@chromium.org> (raw)
Industrial I/O devices can sometimes take a long time to resume,
allowing them to be asynchronus saves 50ms on one light sensor
Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
---
drivers/staging/iio/industrialio-core.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/iio/industrialio-core.c b/drivers/staging/iio/industrialio-core.c
index 768f448..a4b099f 100644
--- a/drivers/staging/iio/industrialio-core.c
+++ b/drivers/staging/iio/industrialio-core.c
@@ -811,6 +811,8 @@ int iio_device_register(struct iio_dev *dev_info)
if (dev_info->modes & INDIO_RING_TRIGGERED)
iio_device_register_trigger_consumer(dev_info);
+ device_enable_async_suspend(&dev_info->dev);
+
return 0;
error_free_sysfs:
--
1.7.2.3
next reply other threads:[~2011-04-06 2:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 2:45 Sonny Rao [this message]
2011-04-06 10:59 ` [PATCH] Enable async suspend/resume on industrial IO devices Jonathan Cameron
2011-04-06 10:59 ` Jonathan Cameron
2011-04-06 22:47 ` Sonny Rao
2011-04-06 22:47 ` Sonny Rao
2011-04-07 11:29 ` Jonathan Cameron
2011-04-07 11:29 ` Jonathan Cameron
2011-04-08 3:26 ` Sonny Rao
2011-04-08 3:26 ` Sonny Rao
2011-04-08 3:26 ` Sonny Rao
2011-04-06 22:47 ` Sonny Rao
-- strict thread matches above, loose matches on Subject: below --
2011-04-06 2:45 Sonny Rao
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=1302057915-13549-1-git-send-email-sonnyrao@chromium.org \
--to=sonnyrao@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bleung@chromium.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--cc=pkurtenbach@gmail.com \
--cc=snanda@chromium.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.