Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v8 8/8] net: e1000e: Adds hardware supported cross timestamp on e1000e nic
Date: Wed, 24 Feb 2016 12:22:44 -0800	[thread overview]
Message-ID: <1456345364.2808.1.camel@intel.com> (raw)
In-Reply-To: <1456139726-3327-9-git-send-email-christopher.s.hall@intel.com>

On Mon, 2016-02-22 at 03:15 -0800, Christopher S. Hall wrote:
> Modern Intel systems supports cross timestamping of the network
> device
> clock and Always Running Timer (ART) in hardware.? This allows the
> device time and system time to be precisely correlated. The timestamp
> pair is returned through e1000e_phc_get_syncdevicetime() used by
> get_system_device_crosststamp().? The hardware cross-timestamp result
> is made available to applications through the PTP_SYS_OFFSET_PRECISE
> ioctl which calls e1000e_phc_getcrosststamp().
> 
> Signed-off-by: Christopher S. Hall <christopher.s.hall@intel.com>
> [jstultz: Reworked to use new interface, commit message tweaks]
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> ---
> ?drivers/net/ethernet/intel/Kconfig????????? |? 9 +++
> ?drivers/net/ethernet/intel/e1000e/defines.h |? 5 ++
> ?drivers/net/ethernet/intel/e1000e/ptp.c???? | 85
> +++++++++++++++++++++++++++++
> ?drivers/net/ethernet/intel/e1000e/regs.h??? |? 4 ++
> ?4 files changed, 103 insertions(+)

Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160224/170bdcbc/attachment.asc>

      reply	other threads:[~2016-02-24 20:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 11:15 [Intel-wired-lan] [PATCH v8 0/8] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 1/8] time: Add cycles to nanoseconds translation Christopher S. Hall
2016-02-24 10:49   ` Thomas Gleixner
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 2/8] time: Add timekeeping snapshot code capturing system time and counter Christopher S. Hall
2016-02-24 10:51   ` Thomas Gleixner
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 3/8] time: Remove duplicated code in ktime_get_raw_and_real() Christopher S. Hall
2016-02-24 10:52   ` Thomas Gleixner
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 4/8] time: Add driver cross timestamp interface for higher precision time synchronization Christopher S. Hall
2016-02-24 10:54   ` Thomas Gleixner
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 5/8] time: Add history to cross timestamp interface supporting slower devices Christopher S. Hall
2016-02-24 10:56   ` Thomas Gleixner
2016-02-24 23:07     ` John Stultz
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-02-24 11:00   ` Thomas Gleixner
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 7/8] ptp: Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2016-02-22 11:15 ` [Intel-wired-lan] [PATCH v8 8/8] net: e1000e: Adds hardware supported cross timestamp on e1000e nic Christopher S. Hall
2016-02-24 20:22   ` Jeff Kirsher [this message]

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=1456345364.2808.1.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.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