From: Greg KH <gregkh@linuxfoundation.org>
To: lakshmi.sowjanya.d@intel.com
Cc: tglx@linutronix.de, giometti@enneenne.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
andriy.shevchenko@linux.intel.com, eddie.dong@intel.com,
christopher.s.hall@intel.com, pandith.n@intel.com,
subramanian.mohan@intel.com, thejesh.reddy.t.r@intel.com
Subject: Re: [PATCH v10 0/3] Add support for Intel PPS Generator
Date: Tue, 13 Aug 2024 10:15:49 +0200 [thread overview]
Message-ID: <2024081330-retouch-platter-f21d@gregkh> (raw)
In-Reply-To: <20240612035359.7307-1-lakshmi.sowjanya.d@intel.com>
On Wed, Jun 12, 2024 at 09:23:56AM +0530, lakshmi.sowjanya.d@intel.com wrote:
> From: Lakshmi Sowjanya D <lakshmi.sowjanya.d@intel.com>
>
> The goal of the PPS (Pulse Per Second) hardware/software is to generate a
> signal from the system on a wire so that some third-party hardware can
> observe that signal and judge how close the system's time is to another
> system or piece of hardware.
>
> Existing methods (like parallel ports) require software to flip a bit at
> just the right time to create a PPS signal. Many things can prevent
> software from doing this precisely. This (Timed I/O) method is better
> because software only "arms" the hardware in advance and then depends on
> the hardware to "fire" and flip the signal at just the right time.
>
> To generate a PPS signal with this new hardware, the kernel wakes up
> twice a second, once for 1->0 edge and other for the 0->1 edge. It does
> this shortly (~10ms) before the actual change in the signal needs to be
> made. It computes the TSC value at which edge will happen, convert to a
> value hardware understands and program this value to Timed I/O hardware.
> The actual edge transition happens without any further action from the
> kernel.
>
> The result here is a signal coming out of the system that is roughly
> 1,000 times more accurate than the old methods. If the system is heavily
> loaded, the difference in accuracy is larger in old methods.
>
> Application Interface:
> The API to use Timed I/O is very simple. It is enabled and disabled by
> writing a '1' or '0' value to the sysfs enable attribute associated with
> the Timed I/O PPS device. Each Timed I/O pin is represented by a PPS
> device. When enabled, a pulse-per-second (PPS) synchronized with the
> system clock is continuously produced on the Timed I/O pin, otherwise it
> is pulled low.
>
> The Timed I/O signal on the motherboard is enabled in the BIOS setup.
> Intel Advanced Menu -> PCH IO Configuration -> Timed I/O <Enable>
>
> References:
> https://en.wikipedia.org/wiki/Pulse-per-second_signal
> https://drive.google.com/file/d/1vkBRRDuELmY8I3FlfOZaEBp-DxLW6t_V/view
> https://youtu.be/JLUTT-lrDqw
>
> Patch 1 adds the pps(pulse per second) generator tio driver to the pps
> subsystem.
> Patch 2 documentation and usage of the pps tio generator module.
> Patch 3 includes documentation for sysfs interface.
>
> These patches are based on the timers/core branch:
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/?h=timers/core
> These changes are dependent on patches that are merged in [1].
This series now breaks the build due to api changes in 6.11-rc1. Please
fix up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-13 8:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 3:53 [PATCH v10 0/3] Add support for Intel PPS Generator lakshmi.sowjanya.d
2024-06-12 3:53 ` [PATCH v10 1/3] pps: generators: Add PPS Generator TIO Driver lakshmi.sowjanya.d
2024-06-12 3:53 ` [PATCH v10 2/3] Documentation: driver-api: pps: Add Intel Timed I/O PPS generator lakshmi.sowjanya.d
2024-06-12 8:02 ` Greg KH
2024-06-12 8:03 ` Greg KH
2024-06-12 3:53 ` [PATCH v10 3/3] ABI: pps: Add ABI documentation for Intel TIO lakshmi.sowjanya.d
2024-06-12 4:29 ` Randy Dunlap
2024-06-12 6:57 ` Rodolfo Giometti
2024-06-12 15:08 ` Randy Dunlap
2024-07-03 14:47 ` [PATCH v10 0/3] Add support for Intel PPS Generator D, Lakshmi Sowjanya
2024-07-04 11:50 ` Rodolfo Giometti
2024-07-15 8:06 ` Thomas Gleixner
2024-07-15 9:36 ` Rodolfo Giometti
2024-07-24 21:39 ` Hall, Christopher S
2024-07-25 7:05 ` Rodolfo Giometti
2024-07-25 7:09 ` gregkh
2024-07-26 11:09 ` Thomas Gleixner
2024-08-13 8:15 ` Greg KH [this message]
2024-08-14 4:36 ` Mohan, Subramanian
2024-08-13 8:25 ` Greg KH
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=2024081330-retouch-platter-f21d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=christopher.s.hall@intel.com \
--cc=corbet@lwn.net \
--cc=eddie.dong@intel.com \
--cc=giometti@enneenne.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pandith.n@intel.com \
--cc=subramanian.mohan@intel.com \
--cc=tglx@linutronix.de \
--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