From: "N, Pandith" <pandith.n@intel.com>
To: "giometti@enneenne.com" <giometti@enneenne.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sangannavar,
Mallikarjunappa" <mallikarjunappa.sangannavar@intel.com>,
"D, Lakshmi Sowjanya" <lakshmi.sowjanya.d@intel.com>,
"T R, Thejesh Reddy" <thejesh.reddy.t.r@intel.com>,
"Hall, Christopher S" <christopher.s.hall@intel.com>
Subject: PPS functionality for Intel Timed I/O
Date: Mon, 30 Jan 2023 12:55:46 +0000 [thread overview]
Message-ID: <BYAPR11MB3240A86B426158623DB9983EE1D39@BYAPR11MB3240.namprd11.prod.outlook.com> (raw)
Hi Rodolfo Giometti,
This is regarding Intel Timed I/O device as PPS.
Intel Timed I/O is a precise device (10s of nanoseconds), that can send out pulses.
This is needed in IoT and server applications to measure offset between system clocks on multiple devices
We are planning to implement a driver, for PPS output functionality using Timed I/O device.
1. Is there any support from PPS framework to start/stop pulse generation.
If yes, can we get the Pin number, offset(start time) from user space ?
2. Further, this device has the capability to capture the input events (pulses, nanosecond precision).
The same PIN can work in either input or output mode.
Can there be an PPS client driver supporting both modes ?
Regards,
Pandith
next reply other threads:[~2023-01-30 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:55 N, Pandith [this message]
2023-01-30 13:45 ` PPS functionality for Intel Timed I/O Rodolfo Giometti
2023-01-30 14:11 ` N, Pandith
2023-01-30 14:26 ` Rodolfo Giometti
2023-02-06 10:16 ` N, Pandith
2023-02-06 10:46 ` Rodolfo Giometti
2023-02-15 7:09 ` N, Pandith
2023-02-15 7:46 ` Rodolfo Giometti
2023-10-06 5:31 ` N, Pandith
2023-10-06 6:23 ` Rodolfo Giometti
2023-10-06 8:34 ` andriy.shevchenko
2023-10-06 8:34 ` andriy.shevchenko
2023-10-06 8:57 ` Rodolfo Giometti
2023-10-06 9:06 ` andriy.shevchenko
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=BYAPR11MB3240A86B426158623DB9983EE1D39@BYAPR11MB3240.namprd11.prod.outlook.com \
--to=pandith.n@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=giometti@enneenne.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=thejesh.reddy.t.r@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;
as well as URLs for NNTP newsgroup(s).