From: Linus Walleij <linus.walleij@linaro.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Gregor Boirie <gregor.boirie@parrot.com>,
Zhang Rui <rui.zhang@intel.com>, Rob Herring <robh+dt@kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Sensors and similar - subsystem interactions, divisions, bindings etc.
Date: Tue, 2 Aug 2016 21:55:37 +0200 [thread overview]
Message-ID: <CACRpkdYM_ACZyHynTQyMJTLzAZtbc+yUbNDmLswxOQt-U6ztGQ@mail.gmail.com> (raw)
In-Reply-To: <579A4A25.9020106@metafoo.de>
On Thu, Jul 28, 2016 at 8:08 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> On 07/28/2016 06:46 PM, Laurent Pinchart wrote:
>> Are you aware of any GPIO
>> hardware that can be programmed to sample at a precise point in time (or
>> perhaps even periodically) ?
>
> I have such hardware. It's custom hardware, non-public at the moment.
>
> But it works like this, for each pin you can configure whether it can be
> controlled independently, like a normal GPIO, or whether the values are
> sampled/updated to/from a continuous data stream that is regularly
> clocked (basically a 1-bit ADC/DAC). This falls right on the edge
> between GPIO and IIO and I'm really torn where to put it. For now I went
> with IIO since it predates the chardev GPIO interface and because of all
> the libiio magic.
I guess either GPIO should reuse the IIO triggers, or we create something
in IIO that uses GPIO from inside the kernel and add get_multiple() as
similar to set_multiple() to the API and thus make a generic GPIO sampler
driver in IIO that can reuse the IIO triggers, while using a plain GPIO
driver as back-end. If the APIs can be made precise enough.
We can even add get_multiple_with_timestamp() if need be to be
able to contain it in gpiolib.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-08-02 19:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 21:18 Jonathan Cameron
2016-07-21 7:39 ` Hans Verkuil
2016-07-22 19:37 ` Jonathan Cameron
2016-07-28 16:50 ` Laurent Pinchart
2016-07-21 19:10 ` Mark Brown
2016-07-22 3:29 ` Guenter Roeck
2016-07-22 4:18 ` Torokhov
2016-07-22 19:01 ` Jonathan Cameron
2016-07-22 10:21 ` Mark Brown
2016-07-22 19:31 ` Jonathan Cameron
2016-07-23 2:29 ` Sebastian Reichel
2016-07-28 21:30 ` Lars-Peter Clausen
2016-07-28 22:39 ` Jonathan Cameron
2016-07-29 0:56 ` Guenter Roeck
2016-07-29 5:54 ` Jonathan Cameron
2016-07-22 12:04 ` Linus Walleij
2016-07-22 19:22 ` Jonathan Cameron
2016-07-28 16:46 ` Laurent Pinchart
2016-07-28 18:08 ` Lars-Peter Clausen
2016-08-02 19:55 ` Linus Walleij [this message]
2016-07-28 22:07 ` Jonathan Cameron
2016-08-02 19:50 ` Linus Walleij
2016-07-27 3:12 ` Vinod Koul
2016-07-28 11:58 ` Mauro Carvalho Chehab
2016-07-28 16:42 ` Laurent Pinchart
2016-07-28 22:09 ` Jonathan Cameron
2016-08-01 11:03 ` Laurent Pinchart
2016-07-29 7:28 ` Hans Verkuil
2016-08-01 11:47 ` Laurent Pinchart
2016-07-28 22:32 ` Jonathan Cameron
2016-07-28 16:39 ` Laurent Pinchart
2016-07-28 18:53 ` Lars-Peter Clausen
2016-07-28 19:46 ` Mark Brown
2016-07-31 17:47 ` Vinod Koul
2016-08-01 12:14 ` Laurent Pinchart
2016-07-28 22:26 ` Jonathan Cameron
2016-07-29 7:36 ` Hans Verkuil
2016-08-01 11:19 ` Laurent Pinchart
2016-07-28 19:12 ` Lars-Peter Clausen
2016-07-28 23:38 ` Alexandre Belloni
2016-07-29 6:04 ` 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=CACRpkdYM_ACZyHynTQyMJTLzAZtbc+yUbNDmLswxOQt-U6ztGQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gregor.boirie@parrot.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@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