From: "Neftin, Sasha" <sasha.neftin@intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>, jeffrey.t.kirsher@intel.com
Cc: intel-wired-lan@lists.osuosl.org,
Anthony Wong <anthony.wong@canonical.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] Opportunistic S0ix blocked by e1000e when ethernet is in use
Date: Mon, 24 Jun 2019 14:56:58 +0300 [thread overview]
Message-ID: <95f88f45-fd6c-52e4-de8c-2db1b4c6c04e@intel.com> (raw)
In-Reply-To: <E2D5225B-D683-4895-AC4F-EE01C339262B@canonical.com>
On 6/24/2019 10:03, Kai-Heng Feng wrote:
> Hi Jeffrey,
>
> at 19:08, Kai-Heng Feng <kai.heng.feng@canonical.com> wrote:
>
>> Hi Jeffrey,
>>
>> There are several platforms that uses e1000e can’t enter Opportunistic
>> S0ix (PC10) when the ethernet has a link partner.
>>
>> This behavior also exits in out-of-tree e1000e driver 3.4.2.1, but
>> seems like 3.4.2.3 fixes the issue.
>>
>> A quick diff between the two versions shows that this code section may
>> be our solution:
>>
>> /* Read from EXTCNF_CTRL in e1000_acquire_swflag_ich8lan function
>> * may occur during global reset and cause system hang.
>> * Configuration space access creates the needed delay.
>> * Write to E1000_STRAP RO register
>> E1000_PCI_VENDOR_ID_REGISTER value
>> * insures configuration space read is done before global reset.
>> */
>> pci_read_config_word(hw->adapter->pdev,
>> E1000_PCI_VENDOR_ID_REGISTER,
>> &pci_cfg);
>> ew32(STRAP, pci_cfg);
>> e_dbg("Issuing a global reset to ich8lan\n");
>> ew32(CTRL, (ctrl | E1000_CTRL_RST));
>> /* cannot issue a flush here because it hangs the hardware */
>> msleep(20);
>>
>> /* Configuration space access improve HW level time sync
>> mechanism.
>> * Write to E1000_STRAP RO register E1000_PCI_VENDOR_ID_REGISTER
>> * value to insure configuration space read is done
>> * before any access to mac register.
>> */
>> pci_read_config_word(hw->adapter->pdev,
>> E1000_PCI_VENDOR_ID_REGISTER,
>> &pci_cfg);
>> ew32(STRAP, pci_cfg);
>
> Turns out the "extra sauce” is not this part, it’s called “Dynamic LTR
> support”.
> >>
>> Is there any plan to support this in the upstream kernel?
>
> Is there any plan to support Dynamic LTR in upstream e1000e?
>
Dynamic LTR is not stable solution. So, we can not put this solution to
upstream. I hope we will be able to fix this in HW for a future projects.
S0ix support is under discussion with our architecture. We will try
enable S0ix in our e1000e OOT driver as first step.
> Kai-Heng
>
>>
>> Kai-Heng
>
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan@osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Thanks
Sasha
next prev parent reply other threads:[~2019-06-24 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 11:08 Kai-Heng Feng
2019-06-24 7:03 ` Kai-Heng Feng
2019-06-24 11:56 ` Neftin, Sasha [this message]
2019-06-24 15:06 ` [Intel-wired-lan] " Kai-Heng Feng
2019-06-25 10:25 ` Neftin, Sasha
2019-06-26 5:49 ` Kai Heng Feng
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=95f88f45-fd6c-52e4-de8c-2db1b4c6c04e@intel.com \
--to=sasha.neftin@intel.com \
--cc=anthony.wong@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®