From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"Manfred.Rudigier@omicron.at" <Manfred.Rudigier@omicron.at>,
"ulrik.debie-os@e2big.org" <ulrik.debie-os@e2big.org>,
"stefan.sorensen@spectralink.com"
<stefan.sorensen@spectralink.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"john.stultz@linaro.org" <john.stultz@linaro.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH net-next 2/3] ptp: igb: Use the high resolution frequency method.
Date: Tue, 8 Nov 2016 22:04:23 +0000 [thread overview]
Message-ID: <1478642646.7545.39.camel@intel.com> (raw)
In-Reply-To: <b1d732324e0b1960b294e90ca5eb2a31b6559188.1478526333.git.richardcochran@gmail.com>
On Tue, 2016-11-08 at 22:49 +0100, Richard Cochran wrote:
> The 82580 and related devices offer a frequency resolution of about
> 0.029 ppb. This patch lets users of the device benefit from the
> increased frequency resolution when tuning the clock.
>
> Signed-off-by: Richard Cochran <richardcochran@gmail.com>
> ---
Additionally, what about min/max frequency check? Wouldn't this need to
be updated for the new adjfine operation?
Thanks,
Jake
next prev parent reply other threads:[~2016-11-08 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 21:49 [PATCH net-next 0/3] PHC frequency fine tuning Richard Cochran
2016-11-08 21:49 ` [PATCH net-next 1/3] ptp: Introduce a high resolution frequency adjustment method Richard Cochran
2016-11-08 21:49 ` [PATCH net-next 2/3] ptp: igb: Use the high resolution frequency method Richard Cochran
2016-11-08 22:02 ` Keller, Jacob E
2016-11-09 13:11 ` Richard Cochran
2016-11-09 21:40 ` Keller, Jacob E
2016-11-08 22:04 ` Keller, Jacob E [this message]
2016-11-09 13:15 ` Richard Cochran
2016-11-08 21:49 ` [PATCH net-next 3/3] ptp: dp83640: " Richard Cochran
2016-11-08 21:56 ` [PATCH net-next 0/3] PHC frequency fine tuning Keller, Jacob E
2016-11-10 2:20 ` David Miller
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=1478642646.7545.39.camel@intel.com \
--to=jacob.e.keller@intel.com \
--cc=Manfred.Rudigier@omicron.at \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.stultz@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=stefan.sorensen@spectralink.com \
--cc=tglx@linutronix.de \
--cc=ulrik.debie-os@e2big.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).