From: Lars-Peter Clausen <lars@metafoo.de>
To: "N, Pandith" <pandith.n@intel.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "vilhelm.gray@gmail.com" <vilhelm.gray@gmail.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"Hall, Christopher S" <christopher.s.hall@intel.com>,
"Sangannavar,
Mallikarjunappa" <mallikarjunappa.sangannavar@intel.com>,
"D, Lakshmi Sowjanya" <lakshmi.sowjanya.d@intel.com>,
"T R, Thejesh Reddy" <thejesh.reddy.t.r@intel.com>
Subject: Re: Intel Timed-IO driver in IIO/Counter subsystem
Date: Fri, 17 Jun 2022 09:22:09 +0200 [thread overview]
Message-ID: <44170bf8-5777-e30b-b74d-a6835b1937e2@metafoo.de> (raw)
In-Reply-To: <BYAPR11MB3240148739EBB945211DD77BE1AF9@BYAPR11MB3240.namprd11.prod.outlook.com>
On 6/17/22 08:37, N, Pandith wrote:
> Hi,
>
> We have a Intel Timed IO peripheral with following functionalities :
>
> 1. Event capture capability - Captures event count and timestamp.
> 2. Pulse generation - periodic or single event generation.
> 3. Return cross-timestamp on request.
>
> Timed IO device is being used in various Industrial use cases such as : time capture, synchronization, fan speed calculation etc.
>
> IIO or counter subsystem seems to be suitable for timed-io driver.
>
> Is it favourable to implement as part of IIO or counter subsystem ? Wanted to know your feedback.
That sounds like a mix of a counter and PPS device. Have you looked at
the PPS subsystem[1]?
[1] https://www.kernel.org/doc/html/latest/driver-api/pps.html
next prev parent reply other threads:[~2022-06-17 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 6:37 Intel Timed-IO driver in IIO/Counter subsystem N, Pandith
2022-06-17 7:22 ` Lars-Peter Clausen [this message]
2022-06-17 9:51 ` Shevchenko, Andriy
2022-06-17 11:39 ` Linus Walleij
2022-06-18 2:01 ` Hall, Christopher S
2022-06-23 12:21 ` Linus Walleij
2022-07-05 3:16 ` Kent Gibson
2022-07-06 5:52 ` Hall, Christopher S
2022-07-06 23:05 ` Linus Walleij
2022-07-07 3:21 ` Kent Gibson
2022-06-17 14:03 ` William Breathitt Gray
2022-06-17 17:15 ` Jonathan Cameron
2022-06-18 1:01 ` Hall, Christopher S
2022-06-21 13:58 ` William Breathitt Gray
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=44170bf8-5777-e30b-b74d-a6835b1937e2@metafoo.de \
--to=lars@metafoo.de \
--cc=andriy.shevchenko@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=jic23@kernel.org \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-iio@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=pandith.n@intel.com \
--cc=thejesh.reddy.t.r@intel.com \
--cc=vilhelm.gray@gmail.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