From: Rodolfo Giometti <giometti@enneenne.com>
To: "N, Pandith" <pandith.n@intel.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: Re: PPS functionality for Intel Timed I/O
Date: Mon, 30 Jan 2023 15:26:55 +0100 [thread overview]
Message-ID: <1e02cc71-baee-1e75-9160-062d563af795@enneenne.com> (raw)
In-Reply-To: <BYAPR11MB3240801F21598EEFAEA79605E1D39@BYAPR11MB3240.namprd11.prod.outlook.com>
On 30/01/23 15:11, N, Pandith wrote:
> Here is a presentation link for Timed I/O device
> https://lpc.events/event/16/contributions/1387/attachments/1051/2010/Timed_IO_LPC.pdf
Thanks. I'll take a look at it.
> Intel Timed I/O PIN has both generator functionality and input capability.
> Wanted to ask if it’s better to have two separate drivers, one under client
> for input and other as generator driver for PPS output.
> OR
> Have a single client driver and user can choose the functionality (either
> PPS output or as PPS source to capture pulses with timestamps).
Within kernel sources PPS clients and PPS generators are placed into different
directories, so I suppose is better to deploy two different pieces of code.
However pay attention to the fact that a PPS generator should be referred to
system's main clock and not to peripherals' clock.
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
next prev parent reply other threads:[~2023-01-30 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:55 PPS functionality for Intel Timed I/O N, Pandith
2023-01-30 13:45 ` Rodolfo Giometti
2023-01-30 14:11 ` N, Pandith
2023-01-30 14:26 ` Rodolfo Giometti [this message]
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=1e02cc71-baee-1e75-9160-062d563af795@enneenne.com \
--to=giometti@enneenne.com \
--cc=christopher.s.hall@intel.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=pandith.n@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).