From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Bernd Faust <berndfaust@gmail.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: fix timing for 82579 Gigabit Ethernet controller
Date: Mon, 27 Feb 2017 10:20:54 +0200 [thread overview]
Message-ID: <d72a8d85-33cd-8bf5-1ed8-0cb8bb3f32a4@intel.com> (raw)
In-Reply-To: <0a95307e-6683-b9fe-1957-be2b0a3c441e@intel.com>
On 2/26/2017 11:08, Neftin, Sasha wrote:
> On 2/19/2017 14:55, Neftin, Sasha wrote:
>> On 2/16/2017 20:42, Bernd Faust wrote:
>>> After an upgrade to Linux kernel v4.x the hardware timestamps of the
>>> 82579 Gigabit Ethernet Controller are different than expected.
>>> The values that are being read are almost four times as big as before
>>> the kernel upgrade.
>>>
>>> The difference is that after the upgrade the driver sets the clock
>>> frequency to 25MHz, where before the upgrade it was set to 96MHz. Intel
>>> confirmed that the correct frequency for this network adapter is 96MHz.
>>>
>>> Signed-off-by: Bernd Faust <berndfaust@gmail.com>
>>> ---
>>> drivers/net/ethernet/intel/e1000e/netdev.c | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c
>>> b/drivers/net/ethernet/intel/e1000e/netdev.c
>>> index 7017281..8b7113d 100644
>>> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
>>> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
>>> @@ -3511,6 +3511,12 @@ s32 e1000e_get_base_timinca(struct
>>> e1000_adapter *adapter, u32 *timinca)
>>>
>>> switch (hw->mac.type) {
>>> case e1000_pch2lan:
>>> + /* Stable 96MHz frequency */
>>> + incperiod = INCPERIOD_96MHz;
>>> + incvalue = INCVALUE_96MHz;
>>> + shift = INCVALUE_SHIFT_96MHz;
>>> + adapter->cc.shift = shift + INCPERIOD_SHIFT_96MHz;
>>> + break;
>>> case e1000_pch_lpt:
>>> if (er32(TSYNCRXCTL) & E1000_TSYNCRXCTL_SYSCFI) {
>>> /* Stable 96MHz frequency */
>>> --
>>> 2.7.4
>>> _______________________________________________
>>> Intel-wired-lan mailing list
>>> Intel-wired-lan@lists.osuosl.org
>>> http://lists.osuosl.org/mailman/listinfo/intel-wired-lan
>>
>> Hello,
>>
>> e1000_pch2lan mac type corresponds to 82579LM and 82579V network
>> adapters. System clock frequency indication (SYSCFI) for these
>> devices supports both 25MHz and 96MHz frequency. By default
>> TSYNCRXCTL.SYSCFI is set to 1 and that means 96MHz frequency is picked.
>>
>> It is better to keep the current implementation as it covers all
>> options.
>>
>> Thanks,
>>
>> Sasha
>>
> Hello,
>
> During last couple of weeks I saw few complaints from community on
> same timing problem with 82579. I will double check clock definition
> with HW architecture.
>
> Sasha
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@lists.osuosl.org
> http://lists.osuosl.org/mailman/listinfo/intel-wired-lan
I've double checked - 82579 support 96MHz frequency only. So, let's
accept this suggestion to upstream.
Ack.
next prev parent reply other threads:[~2017-02-27 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:42 [PATCH] e1000e: fix timing for 82579 Gigabit Ethernet controller Bernd Faust
2017-02-19 12:55 ` [Intel-wired-lan] " Neftin, Sasha
2017-02-26 9:08 ` Neftin, Sasha
2017-02-27 8:20 ` Neftin, Sasha [this message]
2017-02-27 8:39 ` Neftin, Sasha
2017-02-28 21:09 ` Keller, Jacob E
2017-03-24 0:43 ` Brown, Aaron F
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=d72a8d85-33cd-8bf5-1ed8-0cb8bb3f32a4@intel.com \
--to=sasha.neftin@intel.com \
--cc=berndfaust@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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