From: Sasha Neftin <sasha.neftin@intel.com>
To: Andrew Lunn <andrew@lunn.ch>, En-Wei WU <en-wei.wu@canonical.com>
Cc: "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
jesse.brandeburg@intel.co, "Nguyen,
Anthony L" <anthony.l.nguyen@intel.com>,
netdev@vger.kernel.org, rickywu0421@gmail.com,
linux-kernel@vger.kernel.org, "Avivi,
Amir" <amir.avivi@intel.com>,
edumazet@google.com, "Neftin, Sasha" <sasha.neftin@intel.com>,
intel-wired-lan@lists.osuosl.org, "Lifshits,
Vitaly" <vitaly.lifshits@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: fix link fluctuations problem
Date: Wed, 8 May 2024 07:46:48 +0300 [thread overview]
Message-ID: <367fc6ac-cad3-4b2b-9456-2859f1bd4be3@intel.com> (raw)
In-Reply-To: <aad721c1-93c4-48bd-9f05-00c4f6301dce@lunn.ch>
On 07/05/2024 15:10, Andrew Lunn wrote:
> On Tue, May 07, 2024 at 11:24:05AM +0200, En-Wei WU wrote:
>>> Why PHY is this?
>> It's the Intel I219-LM, and I haven't found any other device having
>> the same issue.
>
> There is no Linux PHY driver for this device, only the code buried in
> the e1000e MAC driver. Sometimes Intel use Marvell PHYs, and there are
> a couple of work arounds in the Marvell PHY driver, which might of
> given you a clue. But not in this case...
In I219-* parts used LSI PHY. This PHY is compliant with the 802.3 IEEE
standard if I recall correctly. Auto-negotiation and link establishment
are processed following the IEEE standard and could vary from platform
to platform but are not violent to the IEEE standard.
En-Wei, My recommendation is not to accept these patches. If you think
there is a HW/PHY problem - open a ticket on Intel PAE.
Sasha
>
> Andrew
prev parent reply other threads:[~2024-05-08 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 9:12 [Intel-wired-lan] [PATCH] e1000e: fix link fluctuations problem Ricky Wu
2024-05-03 5:33 ` Paul Menzel
2024-05-03 7:44 ` En-Wei WU
2024-05-07 1:39 ` Andrew Lunn
2024-05-07 9:24 ` En-Wei WU
2024-05-07 12:10 ` Andrew Lunn
2024-05-08 4:46 ` Sasha Neftin [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=367fc6ac-cad3-4b2b-9456-2859f1bd4be3@intel.com \
--to=sasha.neftin@intel.com \
--cc=amir.avivi@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=en-wei.wu@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.co \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rickywu0421@gmail.com \
--cc=vitaly.lifshits@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).