From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] phy: marvell: Fix reg-init bug on 88E1510
Date: Mon, 15 Feb 2016 00:21:26 +0100 [thread overview]
Message-ID: <20160214232125.GA17835@archie.tuxnet.lan> (raw)
In-Reply-To: <20160214204822.GB4802@lunn.ch>
On Sun, Feb 14, 2016 at 09:48:22PM +0100, Andrew Lunn wrote:
> On Sun, Feb 14, 2016 at 09:31:25PM +0100, Clemens Gruber wrote:
> > The function marvell_of_reg_init was called too late, in
> > m88e1510_config_aneg. This function was not reached, due to the phy
> > state machine being stuck at waiting for interrupts (which were not
> > enabled and off by default on the 88E1510)
> > It lead to the ethernet link not coming up at boot.
> >
> > This commit moves the call of marvell_of_reg_init to config_init.
> > Now, a marvell,reg-init option to enable PHY interrupts on pin LED[2] is
> > set early on and the phy state machine does not get stuck anymore.
> > Tested on i.MX6Q boards with Marvell 88E1510 PHYs.
>
> This looks like a good fix for you board. But maybe we should look at
> the bigger picture. How about calling your new
>
> > +static int m88e1510_config_init(struct phy_device *phydev)
> > +{
> > + int err;
> > +
> > + err = marvell_of_reg_init(phydev);
> > + if (err < 0)
> > + return err;
> > +
> > + return 0;
> > +}
>
> marvell_config_init() and adding it to all PHYs which don't have a
> specific config_init function.
>
> We then get more consistent behaviour across Marvell PHYs.
Sounds good. I'll send a new patch tomorrow!
Thanks,
Clemens
prev parent reply other threads:[~2016-02-14 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 20:31 [PATCH] phy: marvell: Fix reg-init bug on 88E1510 Clemens Gruber
2016-02-14 20:48 ` Andrew Lunn
2016-02-14 23:21 ` Clemens Gruber [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=20160214232125.GA17835@archie.tuxnet.lan \
--to=clemens.gruber@pqgruber.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 NNTP newsgroup(s).