From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Francesco Dolcini <francesco.dolcini@toradex.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev <netdev@vger.kernel.org>, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Tim Harvey <tharvey@gateworks.com>
Subject: Re: FEC MDIO read timeout on linkup
Date: Fri, 29 Apr 2022 17:15:13 +0200 [thread overview]
Message-ID: <20220429151513.GA28631@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220422160400.GA527505@francesco-nb.int.toradex.com>
On Fri, Apr 22, 2022 at 06:04:00PM +0200, Francesco Dolcini wrote:
> On Fri, Apr 22, 2022 at 12:55:22PM -0300, Fabio Estevam wrote:
> > On Fri, Apr 22, 2022 at 12:26 PM Francesco Dolcini
> > <francesco.dolcini@toradex.com> wrote:
> > > What I can see from the code is that the timeout is coming from
> > > net/phy/micrel.c:kszphy_handle_interrupt().
> >
> > For debugging purposes, could you try not to describe the Ethernet PHY
> > irq pin inside imx6qdl-apalis.dtsi?
> Yep, we'll try to see what's going on with polling instead that having the
> interrupt enabled.
So, I was not able to reproduce the issue polling the phy instead of
using interrupt. I gonna investigate more in the direction of a race
condition somewhere, unfortunately I had very limited time to work on
this in the last days.
Francesco
next prev parent reply other threads:[~2022-04-29 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 15:26 FEC MDIO read timeout on linkup Francesco Dolcini
2022-04-22 15:55 ` Fabio Estevam
2022-04-22 16:04 ` Francesco Dolcini
2022-04-29 15:15 ` Francesco Dolcini [this message]
2022-05-02 17:05 ` Francesco Dolcini
2022-05-02 18:21 ` Andrew Lunn
2022-05-02 18:25 ` Francesco Dolcini
2022-05-02 18:24 ` Andrew Lunn
2022-05-02 18:34 ` Francesco Dolcini
2022-05-03 16:13 ` Francesco Dolcini
2022-05-03 22:17 ` Andrew Lunn
2022-05-05 8:29 ` Francesco Dolcini
2022-05-05 17:41 ` Andrew Lunn
2022-05-05 17:54 ` 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=20220429151513.GA28631@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qiangqing.zhang@nxp.com \
--cc=tharvey@gateworks.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