linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Felipe Balbi <balbi@ti.com>, <jic23@kernel.org>,
	<linux-iio@vger.kernel.org>
Subject: Re: [RFC/PATCH] iio: light: add support for TI's opt3001 ligth sensor
Date: Wed, 6 Aug 2014 17:38:42 -0500	[thread overview]
Message-ID: <20140806223842.GG3556@saruman.home> (raw)
In-Reply-To: <alpine.DEB.2.01.1408070032040.7595@pmeerw.net>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Thu, Aug 07, 2014 at 12:35:11AM +0200, Peter Meerwald wrote:
> 
> > > > ok... but then that brings up a doubt. What would I use triggered buffer
> > > > for ? I already setup High/Low limits (thresholds) through
> > > > .write_event_value(). Isn't that, pretty much, a triggered buffer ?
> > > 
> > > a triggered buffer reads data from the device and stores it into a buffer 
> > > whenever the trigger goes off (you are interested to capture all samples)
> > 
> > Alright, so something like a contious capture starting after a GPIO goes
> > off, or something ?
> 
> right, one capture whenever the GPIO becomes active typically
>  
> > > events are created on certain conditions (you are not interested in all 
> > > samples)
> > 
> > And this would be more like e.g. "tell me once I have 100 lux or more" ?
> 
> yes

cool thanks. I'll wait for some more review comments before sending a
new version. Latest is kept at [1]

[1] https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/log/?h=opt3001

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-08-06 22:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 16:10 [RFC/PATCH] iio: light: add support for TI's opt3001 ligth sensor Felipe Balbi
2014-08-06 21:11 ` Peter Meerwald
2014-08-06 21:42   ` Felipe Balbi
2014-08-06 22:09     ` Peter Meerwald
2014-08-06 22:18       ` Felipe Balbi
2014-08-06 22:25         ` Peter Meerwald
2014-08-06 22:30           ` Felipe Balbi
2014-08-06 22:35             ` Peter Meerwald
2014-08-06 22:38               ` Felipe Balbi [this message]
2014-08-07 10:13                 ` Jonathan Cameron
2014-08-07 10:08     ` Jonathan Cameron
2014-08-07 14:39       ` Felipe Balbi
2014-08-07 16:27         ` Jonathan Cameron
2014-08-07 16:36           ` Felipe Balbi
2014-08-07 17:00             ` Jonathan Cameron
2014-08-07 10:01 ` Jonathan Cameron
2014-08-07 14:28   ` Felipe Balbi
2014-08-07 16:26     ` Jonathan Cameron
2014-08-07 16:30       ` Jonathan Cameron
2014-08-07 16:35       ` Felipe Balbi
2014-08-07 16:58         ` Jonathan Cameron
2014-08-07 17:54           ` Felipe Balbi
2014-08-11 14:34 ` [RFC/PATCH v2] " Felipe Balbi
2014-08-11 14:46   ` Peter Meerwald
2014-08-11 14:58     ` Felipe Balbi

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=20140806223842.GG3556@saruman.home \
    --to=balbi@ti.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).