All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis CIOCCA <denis.ciocca@st.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Denis Ciocca <denis.ciocca@gmail.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: Use buffer without trigger
Date: Mon, 20 May 2013 09:54:37 +0200	[thread overview]
Message-ID: <2222129.ltZC4niTHM@ctocwl0124> (raw)
In-Reply-To: <519755D6.10000@kernel.org>

On Saturday, May 18, 2013 12:20:06 PM Jonathan Cameron wrote:
> On 05/17/2013 01:52 PM, Lars-Peter Clausen wrote:
> > On 05/17/2013 02:34 PM, Denis CIOCCA wrote:
> >>> Yes, but you still have to assign the trigger to the device in sysfs.
> >>=20
> >> Ok but I have to use a dummy trigger for every device?
> >>=20
> >> Denis
> >=20
> > No. Allocate your buffers and allocate your one trigger. Before you can
> > enable your buffer you need to assign the trigger to the buffer in sysf=
s
> > (By writing to trigger/current_trigger).
>=20
> Lots of the ADC drivers do this.  See max1363 for example. No sign a trig=
ger
> but it definitely has a buffer.  Often these parts convert on demand but
> can do it at very high rates.

Ok, I will look!

Thanks Jonathan & Lars,

Denis=

  reply	other threads:[~2013-05-20  7:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEE_umrLpNJo1kMbLtktK0RH6WCKCEYR+yiTiyPJu_8G3coE7A@mail.gmail.com>
2013-05-14 16:18 ` Use buffer without trigger Denis Ciocca
2013-05-14 17:57   ` Lars-Peter Clausen
2013-05-17 11:28     ` Denis CIOCCA
2013-05-17 11:30       ` Lars-Peter Clausen
2013-05-17 12:34         ` Denis CIOCCA
2013-05-17 12:52           ` Lars-Peter Clausen
2013-05-18 10:20             ` Jonathan Cameron
2013-05-20  7:54               ` Denis CIOCCA [this message]
2013-05-20 12:45               ` Denis CIOCCA

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=2222129.ltZC4niTHM@ctocwl0124 \
    --to=denis.ciocca@st.com \
    --cc=denis.ciocca@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.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.