From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lakshmi.sowjanya.d@intel.com
Cc: tglx@linutronix.de, jstultz@google.com, giometti@enneenne.com,
corbet@lwn.net, linux-kernel@vger.kernel.org, x86@kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, eddie.dong@intel.com,
christopher.s.hall@intel.com, jesse.brandeburg@intel.com,
davem@davemloft.net, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, mcoquelin.stm32@gmail.com, perex@perex.cz,
linux-sound@vger.kernel.org, anthony.l.nguyen@intel.com,
pandith.n@intel.com, mallikarjunappa.sangannavar@intel.com,
thejesh.reddy.t.r@intel.com
Subject: Re: [RFC PATCH v3 00/11] Add support for Intel PPS Generator
Date: Sat, 6 Jan 2024 17:20:10 +0200 [thread overview]
Message-ID: <ZZlvqvYQQuse_P4E@smile.fi.intel.com> (raw)
In-Reply-To: <20240103115602.19044-1-lakshmi.sowjanya.d@intel.com>
On Wed, Jan 03, 2024 at 05:25:51PM +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.
> Facebook and Google are the customers that use this feature.
>
> 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.
At some point you should announce v1 of the series. RFC is usually being
neglected by many (busy) maintainers.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-01-06 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 11:55 [RFC PATCH v3 00/11] Add support for Intel PPS Generator lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 01/11] x86/tsc: Add base clock properties in clocksource structure lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 02/11] timekeeping: Add function to convert realtime to base clock lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 03/11] e10002: remove convert_art_to_tsc() lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 04/11] igc: " lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 05/11] stmmac: intel: " lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 06/11] ALSA: hda: " lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 07/11] ice/ptp: " lakshmi.sowjanya.d
2024-01-03 11:55 ` [RFC PATCH v3 08/11] x86/tsc: Remove art to tsc conversion functions which are obsolete lakshmi.sowjanya.d
2024-01-03 11:56 ` [RFC PATCH v3 09/11] pps: generators: Add PPS Generator TIO Driver lakshmi.sowjanya.d
2024-01-03 11:56 ` [RFC PATCH v3 10/11] Documentation: driver-api: pps: Add Intel Timed I/O PPS generator lakshmi.sowjanya.d
2024-01-03 22:13 ` Randy Dunlap
2024-01-03 11:56 ` [RFC PATCH v3 11/11] ABI: pps: Add ABI documentation for Intel TIO lakshmi.sowjanya.d
2024-01-04 0:24 ` [Intel-wired-lan] " Paul Menzel
2024-01-06 15:20 ` Andy Shevchenko [this message]
2024-01-09 6:31 ` [RFC PATCH v3 00/11] Add support for Intel PPS Generator D, Lakshmi Sowjanya
2024-01-11 11:44 ` Peter Hilber
2024-01-16 5:40 ` D, Lakshmi Sowjanya
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=ZZlvqvYQQuse_P4E@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=anthony.l.nguyen@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=eddie.dong@intel.com \
--cc=giometti@enneenne.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=joabreu@synopsys.com \
--cc=jstultz@google.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pandith.n@intel.com \
--cc=perex@perex.cz \
--cc=tglx@linutronix.de \
--cc=thejesh.reddy.t.r@intel.com \
--cc=x86@kernel.org \
/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).