Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v2 0/5] igc: Add basic support for Timestamping/PTP
Date: Tue, 26 Nov 2019 17:04:30 -0800	[thread overview]
Message-ID: <20191127010435.1733698-1-vinicius.gomes@intel.com> (raw)

Hi,

Changes from v1:
  - Fixed wrong value for IGC_SRRCTL_TIMESTAMP;
  - Added support for retrieving timestamps from PHY (patch 5/5);

Original cover letter (lightly edited):

This adds basic support for Timestamping and enables ptp4l/phc2sys to
work using i225.

To get ptp4l/phc2sys to work we need 2 basic feature sets:
 (1) reading/adjusting the PHC clock;
 (2) enabling/retrieving HW timestamps;

Patch 1/5 adds support for (1), patch 2/5 and 3/5 adds support for (2)
and patch 4/5 implements the ethtool ioctl that ptp4l uses to check
what timestamping methods are supported.

As most of the functionality is similar to i210, this code uses that
as a base. To keep this short, only the features necessary to make
time synchronization using linuxptp are added.

The most important differences from i210 is that there's now support
for multiple PTP domains, with multiple timestamping registers.

Still aiming to keep this series short, only support for one PTP
domain is added, and also only one of the timestamping registers is
used.

Missing from this series is also support configuring/using the
programmable pins.


Cheers,
--
Vinicius

Vinicius Costa Gomes (5):
  igc: Add basic skeleton for PTP
  igc: Add support for RX timestamping
  igc: Add support for TX timestamping
  igc: Add support for ethtool GET_TS_INFO command
  igc: Use Start of Packet signal from PHY for timestamping

 drivers/net/ethernet/intel/igc/Makefile      |   2 +-
 drivers/net/ethernet/intel/igc/igc.h         |  45 ++
 drivers/net/ethernet/intel/igc/igc_defines.h |  66 ++
 drivers/net/ethernet/intel/igc/igc_ethtool.c |  34 +
 drivers/net/ethernet/intel/igc/igc_main.c    |  86 +++
 drivers/net/ethernet/intel/igc/igc_ptp.c     | 716 +++++++++++++++++++
 drivers/net/ethernet/intel/igc/igc_regs.h    |  27 +
 7 files changed, 975 insertions(+), 1 deletion(-)
 create mode 100644 drivers/net/ethernet/intel/igc/igc_ptp.c

-- 
2.24.0


             reply	other threads:[~2019-11-27  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27  1:04 Vinicius Costa Gomes [this message]
2019-11-27  1:04 ` [Intel-wired-lan] [next-queue PATCH v2 1/5] igc: Add basic skeleton for PTP Vinicius Costa Gomes
2019-11-27  1:04 ` [Intel-wired-lan] [next-queue PATCH v2 2/5] igc: Add support for RX timestamping Vinicius Costa Gomes
2019-11-27  1:04 ` [Intel-wired-lan] [next-queue PATCH v2 3/5] igc: Add support for TX timestamping Vinicius Costa Gomes
2019-11-27  1:04 ` [Intel-wired-lan] [next-queue PATCH v2 4/5] igc: Add support for ethtool GET_TS_INFO command Vinicius Costa Gomes
2019-11-27  1:04 ` [Intel-wired-lan] [next-queue PATCH v2 5/5] igc: Use Start of Packet signal from PHY for timestamping Vinicius Costa Gomes

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=20191127010435.1733698-1-vinicius.gomes@intel.com \
    --to=vinicius.gomes@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