From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] phy: phy_update_status wait auto neg done when enabled
Date: Wed, 14 Nov 2012 13:04:36 +0100 [thread overview]
Message-ID: <20121114120436.GL10369@pengutronix.de> (raw)
In-Reply-To: <20121114093458.GH25679@game.jcrosoft.org>
On Wed, Nov 14, 2012 at 10:34:58AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 09:05 Wed 14 Nov , Sascha Hauer wrote:
> > On Tue, Nov 13, 2012 at 10:14:05PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > >
> > > int phy_update_status(struct phy_device *dev)
> > > {
> > > @@ -35,11 +54,18 @@ int phy_update_status(struct phy_device *dev)
> > > struct eth_device *edev = dev->attached_dev;
> > > int ret;
> > > int oldspeed = dev->speed, oldduplex = dev->duplex;
> > > + int old_link = dev->link;
> > >
> > > ret = drv->read_status(dev);
> > > if (ret)
> > > return ret;
> > >
> > > + if (dev->link && !old_link) {
> > > + ret = phy_wait_aneg_read_status(dev, drv);
> > > + if (ret)
> > > + return ret;
> > > + }
> >
> > This does not help. dev->link is false after reset, so we never get into
> > phy_wait_aneg_read_status() which waits for a link.
> read_status update the dev->link as we call update_link
>
> if !dev->link means no cable detected
How should the phy detect the cable if we do not wait for it being
detected?
Here's what I get from my board:
> barebox@Freescale i.MX53 LOCO:/ dhcp
> r 0x0000 0x0001 0x7809
BMSR_ANEGCOMPLETE (1<<5) not set, this means autonegotiation is not complete
> r 0x0000 0x0004 0x01e1
> r 0x0000 0x0000 0x3000
> r 0x0000 0x0001 0x7809
Still not complete,
> r 0x0000 0x0001 0x7809
> r 0x0000 0x0005 0x0001
> r 0x0000 0x0004 0x01e1
> dhcp failed: Network is down
but we do not wait for it, so network down
> dhcp: Network is down
> barebox@Freescale i.MX53 LOCO:/ dhcp
> r 0x0000 0x0001 0x782d
Next try, a few seconds later. BMSR_ANEGCOMPLETE is set, autonegotiation is complete,
BMSR_LSTATUS showd that link status is up.
> r 0x0000 0x0001 0x782d
> r 0x0000 0x0005 0x45e1
> r 0x0000 0x0004 0x01e1
> 100Mbps full duplex link detected
And it works.
I do not believe that this behaviour is specific to the special phy on
this board.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-11-14 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 21:14 Jean-Christophe PLAGNIOL-VILLARD
2012-11-14 8:05 ` Sascha Hauer
2012-11-14 9:34 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-14 12:04 ` Sascha Hauer [this message]
2012-11-14 17:24 ` Jean-Christophe PLAGNIOL-VILLARD
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=20121114120436.GL10369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.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