public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	bruce.w.allan@intel.com, Jacob Keller <jacob.e.keller@intel.com>,
	John Ronciak <john.ronciak@intel.com>,
	Matthew Vick <matthew.vick@intel.com>, Jian Yu <jian.yu@ni.com>,
	Richard Cochran <rcochran@linutronix.de>
Subject: Re: [PATCH net-next V2 0/4] igb: auxiliary PHC functions for the i210.
Date: Fri, 21 Nov 2014 04:37:55 -0800	[thread overview]
Message-ID: <1416573475.2280.35.camel@jtkirshe-mobl> (raw)
In-Reply-To: <cover.1416562191.git.rcochran@linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]

On Fri, 2014-11-21 at 10:41 +0100, Richard Cochran wrote:
> From: Richard Cochran <rcochran@linutronix.de>
> 
> * ChangeLog
> ** V2
>    - Add missing serialization in the reset function
>    - Reset the auxiliary functions along with the rest
>    - Guard against spurious SYS_WRAP interrupts (these occur in the
>      82580 device from time to time)
> 
> This patch series adds three features: time stamping external events,
> producing a periodic output signal, and an internal PPS event. The
> i210 PCIe card has a 6 pin header with SDP0-3, making it easy to try
> out this new functionality.
> 
> An earlier version of this series was posted way back in May, 2013,
> but that version lacked a good way to assign functions to the pins. In
> the mean time, the PHC core has a standard method to configure the
> pins, and this series makes use of it.
> 
> Thanks,
> Richard
> 
> Richard Cochran (4):
>   igb: refactor time sync interrupt handling
>   igb: serialize access to the time sync interrupt registers.
>   igb: enable internal PPS for the i210.
>   igb: enable auxiliary PHC functions for the i210.
> 
>  drivers/net/ethernet/intel/igb/igb.h      |    9 +
>  drivers/net/ethernet/intel/igb/igb_main.c |  110 +++++++++----
>  drivers/net/ethernet/intel/igb/igb_ptp.c  |  254
> ++++++++++++++++++++++++++++-
>  3 files changed, 337 insertions(+), 36 deletions(-)

Thanks Richard, I have added your series to my queue.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2014-11-21 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  9:41 [PATCH net-next V2 0/4] igb: auxiliary PHC functions for the i210 Richard Cochran
2014-11-21  9:41 ` [PATCH net-next V2 1/4] igb: refactor time sync interrupt handling Richard Cochran
2014-11-21  9:41 ` [PATCH net-next V2 2/4] igb: serialize access to the time sync interrupt registers Richard Cochran
2014-11-21  9:41 ` [PATCH net-next V2 3/4] igb: enable internal PPS for the i210 Richard Cochran
2014-11-21  9:41 ` [PATCH net-next V2 4/4] igb: enable auxiliary PHC functions " Richard Cochran
2014-11-21 12:46   ` Jeff Kirsher
2014-11-21 12:59     ` Richard Cochran
2014-11-21 12:37 ` 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=1416573475.2280.35.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=jacob.e.keller@intel.com \
    --cc=jian.yu@ni.com \
    --cc=john.ronciak@intel.com \
    --cc=matthew.vick@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=rcochran@linutronix.de \
    --cc=richardcochran@gmail.com \
    /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