From: Lars-Peter Clausen <lars@metafoo.de>
To: Crt Mori <cmo@melexis.com>,
Crestez Dan Leonard <leonard.crestez@intel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Daniel Baluta <daniel.baluta@intel.com>,
Thierry Reding <thierry.reding@avionic-design.de>
Subject: Re: [PATCH 2/2] ti-adc081c: Initial triggered buffer support
Date: Fri, 1 Apr 2016 11:23:07 +0200 [thread overview]
Message-ID: <56FE3DFB.5050409@metafoo.de> (raw)
In-Reply-To: <CAKv63uuo-q0W+J2=MWVSpxaHFG4JFvjsHHGx8cwLHq_ZWdD1Jw@mail.gmail.com>
On 04/01/2016 10:08 AM, Crt Mori wrote:
> On 31 March 2016 at 19:20, Crestez Dan Leonard
> <leonard.crestez@intel.com> wrote:
>> Using this requires software triggers like CONFIG_IIO_HRTIMER_TRIGGER.
> Then we are missing DEPENDS in Kconfig...
The device could be used with any generic trigger. The device driver
shouldn't make the choice here which one it requires and which one not.
- Lars
next prev parent reply other threads:[~2016-04-01 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 17:20 [PATCH 0/2] Add support for adc101c* and adc121c* Crestez Dan Leonard
2016-03-31 17:20 ` [PATCH 1/2] ti-adc081c: " Crestez Dan Leonard
2016-04-01 8:17 ` Peter Meerwald-Stadler
2016-04-03 9:16 ` Jonathan Cameron
2016-03-31 17:20 ` [PATCH 2/2] ti-adc081c: Initial triggered buffer support Crestez Dan Leonard
2016-04-01 8:08 ` Crt Mori
2016-04-01 9:23 ` Lars-Peter Clausen [this message]
2016-04-01 8:34 ` Peter Meerwald-Stadler
2016-04-01 11:13 ` Leonard Crestez
2016-04-03 9:25 ` Jonathan Cameron
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=56FE3DFB.5050409@metafoo.de \
--to=lars@metafoo.de \
--cc=cmo@melexis.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=leonard.crestez@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=thierry.reding@avionic-design.de \
/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).