From: Andrew Lunn <andrew@lunn.ch>
To: Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: Vitaly Lifshits <vitaly.lifshits@intel.com>,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: Link flap workaround option for false IRP events
Date: Tue, 4 Mar 2025 23:24:05 +0100 [thread overview]
Message-ID: <eb5b93b5-ca90-4287-b6b5-17825d79e6ea@lunn.ch> (raw)
In-Reply-To: <a2bd6964-1ec0-4bd6-ad68-7210ac3fe38b@app.fastmail.com>
> > I suggest to try replacing the register read for a short delay or
> > reading the PHY STATUS register instead.
> >
>
> Ack - we'll try that, and collect some other debug registers in the process.
> Will update with findings - this may take a while :)
Please be careful with which register you choice. Because the link
status bit in BMSR is latching, you should not be reading it and
discarding the result.
Reading register 2 or 3 should be totally safe.
Another thing to keep in mind, you cannot unconditionally read a paged
register in this particular PHY, because the e1000e is used with a
number of different PHYs. That register does not exist in other PHYs,
and the action of selecting the page performs a register write, which
for some other PHY could be destructive. So i would suggest you keep
to registers defined in 802.3 C22.
Andrew
next prev parent reply other threads:[~2025-03-04 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:44 Mark Pearson
2025-02-26 22:52 ` Andrew Lunn
2025-02-27 15:05 ` Mark Pearson
2025-02-27 16:02 ` Andrew Lunn
2025-02-27 16:07 ` Andrew Lunn
2025-02-28 14:59 ` Mark Pearson
2025-02-28 16:37 ` Andrew Lunn
2025-03-02 13:09 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-03-02 16:13 ` Andrew Lunn
2025-03-03 3:34 ` Mark Pearson
2025-03-04 10:48 ` Lifshits, Vitaly
2025-03-04 13:41 ` Andrew Lunn
2025-03-04 14:12 ` Mark Pearson
2025-03-04 22:24 ` Andrew Lunn [this message]
2025-03-03 3:05 ` Mark Pearson
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=eb5b93b5-ca90-4287-b6b5-17825d79e6ea@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®