[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d4c72cf9-930d-7559-9ca8-3336626e29d9@molgen.mpg.de>
Date: Thu, 24 Sep 2020 15:02:36 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: Kai-Heng Feng <kai.heng.feng@...onical.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: Power cycle phy on PM resume
Dear Andrew,
Am 23.09.20 um 21:28 schrieb Andrew Lunn:
>>>> How much does this increase the resume time?
>
> Define resume time? Until you get the display manager unlock screen?
> Or do you need working networking?
Until network is functional again. Currently, the speed negotiation
alone takes three(?) seconds, so making it even longer is unacceptable.
(You wrote it below.)
> It takes around 1.5 seconds for auto negotiation to get a link. I know
> it takes me longer than that to move my fingers to the keyboard and
> type in my password to unlock the screen. So by the time you actually
> get to see your desktop, you should have link.
Not here.
> I've no idea about how the e1000e driver does link negotiation. But
> powering the PHY off means there is going to be a negotiation sometime
> later. But if you don't turn it off, the driver might be able to avoid
> doing an autoneg if the PHY has already done one when it got powered
> up.
Indeed.
Kind regards,
Paul
Powered by blists - more mailing lists