From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
jacob.e.keller@intel.com, matthew.vick@intel.com
Subject: Re: [PATCH net-next] net: igb: implement high frequency periodic output signals
Date: Wed, 08 Jul 2015 16:14:17 -0700 [thread overview]
Message-ID: <1436397257.3214.14.camel@intel.com> (raw)
In-Reply-To: <20150708.161150.1028571714100873421.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
On Wed, 2015-07-08 at 16:11 -0700, David Miller wrote:
> From: Richard Cochran <richardcochran@gmail.com>
> Date: Tue, 7 Jul 2015 16:41:42 +0200
>
> > In addition to interrupt driven target time output events, the i210
> > also has two programmable clock outputs. These clocks support
> periods
> > between 16 nanoseconds and 140 milliseconds. This patch implements
> > the periodic output function using the clock outputs when possible,
> > falling back to the target time for longer periods.
> >
> > Signed-off-by: Richard Cochran <richardcochran@gmail.com>
>
> I assume I will get this via the Intel folks in a future pull request.
Correct, I will be adding it to my queue.
Richard- FYI for the future, could you at least CC
intel-wired-lan@lists.osuosl.org on the Intel wired LAN patches. It
helps me keep track of patches against our drivers. Thanks!
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-07-08 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 14:41 [PATCH net-next] net: igb: implement high frequency periodic output signals Richard Cochran
2015-07-08 23:11 ` David Miller
2015-07-08 23:14 ` 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=1436397257.3214.14.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=jacob.e.keller@intel.com \
--cc=matthew.vick@intel.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).