From: Andrew Lunn <andrew@lunn.ch>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: Fix phy_modify() semantic difference fallout
Date: Tue, 9 Jan 2018 15:10:08 +0100 [thread overview]
Message-ID: <20180109141008.GD27447@lunn.ch> (raw)
In-Reply-To: <1515496281-10988-1-git-send-email-geert+renesas@glider.be>
On Tue, Jan 09, 2018 at 12:11:21PM +0100, Geert Uytterhoeven wrote:
> In case of success, the return values of (__)phy_write() and
> (__)phy_modify() are not compatible: (__)phy_write() returns 0, while
> (__)phy_modify() returns the old PHY register value.
>
> Apparently this change was catered for in drivers/net/phy/marvell.c, but
> not in other source files.
>
> Hence genphy_restart_aneg() now returns 4416 instead zero, which is
> considered an error:
>
> ravb e6800000.ethernet eth0: failed to connect PHY
> IP-Config: Failed to open eth0
> IP-Config: No network devices available
>
> Fix this by converting positive values to zero in all callers of
> phy_modify().
>
> Fixes: fea23fb591cce995 ("net: phy: convert read-modify-write to phy_modify()")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Alternatively, __phy_modify() could be changed to follow __phy_write()
> semantics?
Hi Geert, Russell
I took a quick look at the uses of phy_modify(). I don't see any uses
of the return code other than as an error indicator. So having it
return 0 on success seems like a better fix.
Andrew
next prev parent reply other threads:[~2018-01-09 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 11:11 [PATCH] net: phy: Fix phy_modify() semantic difference fallout Geert Uytterhoeven
2018-01-09 14:10 ` Andrew Lunn [this message]
2018-01-09 14:22 ` Russell King - ARM Linux
2018-01-09 14:35 ` Geert Uytterhoeven
2018-01-09 14:48 ` Andrew Lunn
2018-01-09 14:50 ` Russell King - ARM Linux
2018-01-09 18:25 ` Geert Uytterhoeven
2018-01-09 18:31 ` Russell King - ARM Linux
2018-01-09 18:36 ` Geert Uytterhoeven
2018-01-09 14:35 ` Niklas Cassel
2018-01-11 15:48 ` David Miller
2018-01-11 15:53 ` Russell King - ARM Linux
2018-01-11 15:54 ` Geert Uytterhoeven
2018-01-11 16:00 ` Geert Uytterhoeven
2018-01-11 16:05 ` Russell King - ARM Linux
2018-01-11 17:04 ` Andrew Lunn
2018-01-11 20:28 ` Florian Fainelli
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=20180109141008.GD27447@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).