From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Clément Leger" <cleger@kalray.eu>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] phy: call adjust_link in attach if using fixed-link
Date: Tue, 16 Oct 2018 08:56:38 +0200 [thread overview]
Message-ID: <20181016065638.t5mwfenlcb4iz5tp@pengutronix.de> (raw)
In-Reply-To: <1034587066.7904413.1539615604832.JavaMail.zimbra@kalray.eu>
On Mon, Oct 15, 2018 at 05:00:04PM +0200, Clément Leger wrote:
> Normally, phy_update_status is in charge of reporting a change in link
> status when phy is updated. When using fixed-link, speed and duplex are
> initialized directly after registering the phy and there is no driver.
> Hence when phy_update_status is called, the check for new values fails
> and returns directly. Since update_link call is mandatory for some
> network devices to work, call it directly when using fixed link in
> phy_device_attach to force update of link.
>
> Signed-off-by: Clement Leger <clement.leger@kalray.eu>
> ---
> drivers/net/phy/phy.c | 4 ++++
> 1 file changed, 4 insertions(+)
Indeed, sounds logical. Applied, thanks
Sascha
>
> diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
> index 42dcad906..63f249fcf 100644
> --- a/drivers/net/phy/phy.c
> +++ b/drivers/net/phy/phy.c
> @@ -398,6 +398,10 @@ static int phy_device_attach(struct phy_device *phy, struct eth_device *edev,
>
> phy->adjust_link = adjust_link;
>
> + /* If the phy is a fixed-link, then call adjust_link directly */
> + if (!phy->bus && adjust_link)
> + adjust_link(edev);
> +
> return 0;
> }
>
> --
> 2.15.0.276.g89ea799
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
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
prev parent reply other threads:[~2018-10-16 6:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 15:00 Clément Leger
2018-10-16 6:56 ` Sascha Hauer [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=20181016065638.t5mwfenlcb4iz5tp@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=cleger@kalray.eu \
/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