From: Richard Cochran <richardcochran@gmail.com>
To: <netdev@vger.kernel.org>
Cc: e1000-devel@lists.sourceforge.net,
Jacob Keller <jacob.e.keller@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
John Ronciak <john.ronciak@intel.com>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH net V4 0/2] igb: ptp hardware clock
Date: Sat, 21 Jan 2012 17:03:50 +0100 [thread overview]
Message-ID: <cover.1327161325.git.richardcochran@gmail.com> (raw)
* ChangeLog
** V4
- Use standard kernel cyclecounter/timecounter infrastructure
instead of a home grown counter overflow implementation.
** V3
- Driver compiles even without CONFIG_PTP_1588_CLOCK.
- Timestamping always works, even when PTP code missing or fails.
** V2
- Fixed wrong bit shifting in the 82576 code.
- Explained the timestamp locking with a comment in the code.
- Preserved the comments from the original timecompare implementation.
- Added an additional test within the overflow counter code to fix
a race condition. Details of the problem are given in the commit
message.
This patch series implements a PHC driver for the Intel 82576 and
82580 devices, as part of the igb driver. Only the base clock
operations are implemented. The hardware does have some ancillary
features, but these can be easily added later.
The first patch adds the PHC driver code as a new source module but
does not link it into the main igb driver. Because the system time
counter is not so very wide, the code uses the overflow counter from
the cyclecounter/timecounter code. Every read operation maintains the
overflow counter, as does a "delayed work" watchdog.
The second patch removes the timecompare code and links in the new
functions.
I have tested the 82580 with good results. However, I don't have the
82576 and so would appreciate testing and feedback.
Thanks,
Richard
Richard Cochran (2):
igb: add PTP Hardware Clock code
igb: offer a PTP Hardware Clock instead of the timecompare method
drivers/net/ethernet/intel/igb/Makefile | 2 +-
drivers/net/ethernet/intel/igb/igb.h | 20 ++-
drivers/net/ethernet/intel/igb/igb_main.c | 167 +------------
drivers/net/ethernet/intel/igb/igb_ptp.c | 388 +++++++++++++++++++++++++++++
4 files changed, 407 insertions(+), 170 deletions(-)
create mode 100644 drivers/net/ethernet/intel/igb/igb_ptp.c
--
1.7.2.5
next reply other threads:[~2012-01-21 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 16:03 Richard Cochran [this message]
2012-01-21 16:03 ` [PATCH net V4 1/2] igb: add PTP Hardware Clock code Richard Cochran
2012-01-23 18:39 ` Keller, Jacob E
2012-01-24 17:44 ` Richard Cochran
2012-01-24 21:23 ` Keller, Jacob E
2012-01-27 19:25 ` Keller, Jacob E
2012-01-21 16:03 ` [PATCH net V4 2/2] igb: offer a PTP Hardware Clock instead of the timecompare method Richard Cochran
2012-01-23 3:57 ` [PATCH net V4 0/2] igb: ptp hardware clock Jeff Kirsher
2012-01-27 4:24 ` Jeff Kirsher
2012-01-27 10:11 ` Richard Cochran
2012-01-27 10:15 ` Jeff Kirsher
2012-01-27 10:22 ` Eric Dumazet
2012-01-27 10:56 ` Jeff Kirsher
2012-01-27 12:11 ` Richard Cochran
2012-01-27 20:42 ` Brown, Aaron F
2012-01-28 8:26 ` Richard Cochran
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=cover.1327161325.git.richardcochran@gmail.com \
--to=richardcochran@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jacob.e.keller@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=john.stultz@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).