From: Andrew Lunn <andrew@lunn.ch>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Praneeth Bajjuri <praneeth@ti.com>, Geet Modi <geet.modi@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Dan Murphy <dmurphy@ti.com>
Subject: Re: DP83867 ethernet PHY regression
Date: Mon, 22 May 2023 17:15:56 +0200 [thread overview]
Message-ID: <e0d4b397-a8d9-4546-a8a2-14cf07914e64@lunn.ch> (raw)
In-Reply-To: <ZGuDJos8D7N0J6Z2@francesco-nb.int.toradex.com>
On Mon, May 22, 2023 at 04:58:46PM +0200, Francesco Dolcini wrote:
> Hello all,
> commit da9ef50f545f ("net: phy: dp83867: perform soft reset and retain
> established link") introduces a regression on my TI AM62 based board.
>
> I have a working DTS with Linux TI 5.10 downstream kernel branch, while
> testing the DTS with v6.4-rc in preparation of sending it to the mailing
> list I noticed that ethernet is working only on a cold poweron.
Do you have more details about how it does not work.
Please could you use:
mii-tool -vvv ethX
in both the good and bad state. The register values might give us a
clue.
Thanks
Andrew
next prev parent reply other threads:[~2023-05-22 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:58 Francesco Dolcini
2023-05-22 15:15 ` Andrew Lunn [this message]
2023-05-22 15:35 ` Francesco Dolcini
2023-05-22 16:15 ` Andrew Lunn
2023-05-25 8:18 ` Alexander Stein
2023-05-24 12:13 ` Andrew Lunn
2023-05-24 12:51 ` Bagas Sanjaya
2023-05-25 6:31 ` Johannes Pointner
2023-05-25 7:33 ` Francesco Dolcini
2023-05-25 8:18 ` Bajjuri, Praneeth
2023-06-15 20:46 ` Francesco Dolcini
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=e0d4b397-a8d9-4546-a8a2-14cf07914e64@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=edumazet@google.com \
--cc=francesco@dolcini.it \
--cc=geet.modi@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=praneeth@ti.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®