From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ns.pmeerw.net ([87.118.82.44]:58517 "EHLO pmeerw.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754037AbaHFWfN (ORCPT ); Wed, 6 Aug 2014 18:35:13 -0400 Date: Thu, 7 Aug 2014 00:35:11 +0200 (CEST) From: Peter Meerwald To: Felipe Balbi cc: jic23@kernel.org, linux-iio@vger.kernel.org Subject: Re: [RFC/PATCH] iio: light: add support for TI's opt3001 ligth sensor In-Reply-To: <20140806223045.GF3556@saruman.home> Message-ID: References: <1407341409-30284-1-git-send-email-balbi@ti.com> <20140806214222.GB3556@saruman.home> <20140806221823.GE3556@saruman.home> <20140806223045.GF3556@saruman.home> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org > > > 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 p. -- Peter Meerwald +43-664-2444418 (mobile)