From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [Regression] "e1000e: Add support for S0ix" breaks s2idle on Lenovo X1 Carbon 7th
Date: Wed, 18 Mar 2020 15:31:28 +0200 [thread overview]
Message-ID: <c94e12da-efb2-5e7f-b6a7-726f0378268b@intel.com> (raw)
In-Reply-To: <C9A08D85-D64B-44DD-8460-3405F2547D53@canonical.com>
On 3/18/2020 14:21, Kai-Heng Feng wrote:
> Hi Sasha,
>
>> On Mar 18, 2020, at 16:50, Neftin, Sasha <sasha.neftin@intel.com> wrote:
>
> [snipped]
>
>> ok, let's understand where is PHY location.
>
> Lenovo confirmed the PHY is inside the laptop.
>
>> Since no docking connected why driver should run?
>
> Because the SoC in the laptop has an I219 device?
>
>> There is no RJ45 port on laptop.
>
> The Lenovo ethernet dongle wires the RJ45 to the I219 device.
>
>> S0ix flow same (I got confirmation from our architecture team) and should haven't impact on Sx.
>> if PHY located externally... during S0ix flow we try access to the PHY and it can be problem. Since laptop have no RJ45 connector driver not expected to run I though.
>
> But the I219 device is always on the PCI bus so e1000e should bind to it?
>
ok. Need to debug this system. We will escalate this problem to our PAE.
> Kai-Heng
>
prev parent reply other threads:[~2020-03-18 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 13:34 [Intel-wired-lan] [Regression] "e1000e: Add support for S0ix" breaks s2idle on Lenovo X1 Carbon 7th Kai-Heng Feng
2020-03-17 13:56 ` Neftin, Sasha
2020-03-17 14:04 ` Kai-Heng Feng
2020-03-17 14:39 ` Vitaly Lifshits
2020-03-18 3:12 ` Kai-Heng Feng
2020-03-18 7:32 ` Neftin, Sasha
2020-03-18 8:23 ` Kai-Heng Feng
2020-03-18 8:50 ` Neftin, Sasha
2020-03-18 12:21 ` Kai-Heng Feng
2020-03-18 13:31 ` Neftin, Sasha [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=c94e12da-efb2-5e7f-b6a7-726f0378268b@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.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