[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D9C477E.4050400@cam.ac.uk>
Date: Wed, 06 Apr 2011 11:59:10 +0100
From: Jonathan Cameron <jic23@....ac.uk>
To: Sonny Rao <sonnyrao@...omium.org>
CC: linux-pm@...ts.linux-foundation.org, bleung@...omium.org,
snanda@...omium.org, Greg Kroah-Hartman <gregkh@...e.de>,
Manuel Stahl <manuel.stahl@....fraunhofer.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Phillip Kurtenbach <pkurtenbach@...il.com>,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>
Subject: Re: [PATCH] Enable async suspend/resume on industrial IO devices
On 04/06/11 03:45, Sonny Rao wrote:
> Industrial I/O devices can sometimes take a long time to resume,
> allowing them to be asynchronus saves 50ms on one light sensor
>
Hi Sonny,
cc'd linux-iio
I'm not particularly familiar with this. Are there any disadvantages?
I just wonder if it would be better to push this into individual drivers
rather than the core?
Jonathan
> Signed-off-by: Sonny Rao <sonnyrao@...omium.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:
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists