From: Jonathan Cameron <jic23@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: accel: BMC150 accel support
Date: Mon, 07 Jul 2014 17:13:56 +0100 [thread overview]
Message-ID: <53BAC744.3070704@kernel.org> (raw)
In-Reply-To: <20140707143600.GA2469@sirena.org.uk>
On 07/07/14 15:36, Mark Brown wrote:
> On Sun, Jun 29, 2014 at 03:42:55PM +0100, Jonathan Cameron wrote:
>> On 29/06/14 15:27, Srinivas Pandruvada wrote:
>
> Please don't use my Linaro address for upstream things, use my
> kernel.org one (which is the one I always use for mail and is in
> MAINTAINERS).
Will do.
>
> I'm also having a bit of an issue reading the mail due to it not being
> word wrapped.
It does indeed seem to have gotten wrapped at a random, somewhat
longer than normal length... Oops.
>
>> If we are dependent on regulators to leave certain states, do we have access to how long
>> they take to start up? What about bringing buses up...
>
>> Cc'd Mark Brown on the basis he knows all sorts of hideous corners of the kernel way
>> better than me ;)
>
> With regulators the delays are handled transparently in the framework -
> by the time the functions return the operation should have commpleted.
> If there is a need to have a non-blocking interface we'll have to add
> this. The delays can be queried with _time() functions.
We are looking at a somewhat tangential question here...
What we have is a device that has various power saving levels. As
the basic interest of IIO is grabbing data, in a sense it is the
time taken to return from a given level and grab some data that
acts as the controlling variable on how low a power state the
device should go into.
Hence rather than picking a given power state (deep sleep or similar)
we want the control to be on capture latency. Hence userspace
can specify the 'worst case' latency it will accept and the
device will hence enter the lowest power state, between samples,
that it can without failing to meet the requirement.
What I was wondering is whether there is anything similar
elsewhere that you know of? For example, could we query a
regulator driver to ask it how long it will take to start up
a given output?
This extension beyond the device it self to it's power supplies
and for example bus is more of an idle thought than an actual
plan at this stage.
J
next prev parent reply other threads:[~2014-07-07 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 18:12 [PATCH] iio: accel: BMC150 accel support Srinivas Pandruvada
2014-06-22 14:23 ` Jonathan Cameron
2014-06-23 1:22 ` Srinivas Pandruvada
2014-06-29 11:12 ` Jonathan Cameron
2014-06-29 14:27 ` Srinivas Pandruvada
2014-06-29 14:42 ` Jonathan Cameron
2014-07-07 14:36 ` Mark Brown
2014-07-07 16:13 ` Jonathan Cameron [this message]
2014-07-08 13:23 ` Mark Brown
2014-07-08 15:27 ` Jonathan Cameron
2014-07-08 18:03 ` Jonathan Cameron
2014-06-29 20:43 ` Peter Meerwald
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=53BAC744.3070704@kernel.org \
--to=jic23@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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).