From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: "Christopher S. Hall" <christopher.s.hall@intel.com>,
tglx@linutronix.de, richardcochran@gmail.com, mingo@redhat.com,
john.stultz@linaro.org, hpa@zytor.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
kevin.b.stanton@intel.com, kevin.j.clarke@intel.com
Subject: Re: [PATCH v7 8/8] net: e1000e: Adds hardware supported cross timestamp on e1000e nic
Date: Thu, 18 Feb 2016 16:43:23 -0800 [thread overview]
Message-ID: <1455842603.3128.61.camel@intel.com> (raw)
In-Reply-To: <1455308729-6280-9-git-send-email-christopher.s.hall@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Fri, 2016-02-12 at 12:25 -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>
I am fine with Christopher's changes, so when the issues with the other
patches in the series gets ironed out, your good to apply this patch as
well John.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-19 0:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:25 [PATCH v7 0/8] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 1/8] time: Add cycles to nanoseconds translation Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 2/8] time: Add timekeeping snapshot code capturing system time and counter Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 3/8] time: Remove duplicated code in ktime_get_raw_and_real() Christopher S. Hall
2016-02-16 7:52 ` Richard Cochran
2016-02-16 18:23 ` Christopher Hall
2016-02-12 20:25 ` [PATCH v7 4/8] time: Add driver cross timestamp interface for higher precision time synchronization Christopher S. Hall
2016-02-16 7:56 ` Richard Cochran
2016-02-12 20:25 ` [PATCH v7 5/8] time: Add history to cross timestamp interface supporting slower devices Christopher S. Hall
2016-02-18 22:17 ` Richard Cochran
2016-02-19 17:33 ` John Stultz
2016-02-12 20:25 ` [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-02-18 21:11 ` Andy Lutomirski
2016-02-23 2:38 ` Christopher Hall
2016-02-23 2:49 ` Andy Lutomirski
2016-02-12 20:25 ` [PATCH v7 7/8] ptp: Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 8/8] net: e1000e: Adds hardware supported cross timestamp on e1000e nic Christopher S. Hall
2016-02-19 0:43 ` Jeff Kirsher [this message]
2016-02-18 19:26 ` [PATCH v7 0/8] Patchset enabling hardware based cross-timestamps for next gen Intel platforms John Stultz
2016-02-22 18:33 ` Christopher Hall
2016-02-22 18:49 ` John Stultz
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=1455842603.3128.61.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=hpa@zytor.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=john.stultz@linaro.org \
--cc=kevin.b.stanton@intel.com \
--cc=kevin.j.clarke@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--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).