From: Kosta Zertsekel <konszert@marvell.com>
To: netdev@vger.kernel.org
Cc: zertsekel@gmail.com, andrew@lunn.ch, benavi@marvell.com,
linux-arm-kernel@lists.infradead.org, alior@marvell.com,
Kosta Zertsekel <konszert@marvell.com>
Subject: [PATCH 1/2] Fix phy_init for Marvell network eth driver
Date: Thu, 10 Jan 2013 14:00:33 +0200 [thread overview]
Message-ID: <1357819234-27752-2-git-send-email-konszert@marvell.com> (raw)
In-Reply-To: <1357819234-27752-1-git-send-email-konszert@marvell.com>
At least it fixes DNS323_REV_C1 board case (mach-orion5x/dsn323-setup.c file).
Change-Id: I37d64795f79c358f66a211a150cec2263e40e295
---
drivers/net/ethernet/marvell/mv643xx_eth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c b/drivers/net/ethernet/marvell/mv643xx_eth.c
index 84c1326..7b8c1ac 100644
--- a/drivers/net/ethernet/marvell/mv643xx_eth.c
+++ b/drivers/net/ethernet/marvell/mv643xx_eth.c
@@ -2789,7 +2789,7 @@ static void phy_init(struct mv643xx_eth_private *mp, int speed, int duplex)
phy_reset(mp);
- phy_attach(mp->dev, dev_name(&phy->dev), 0, PHY_INTERFACE_MODE_GMII);
+ phy_attach(mp->dev, dev_name(&phy->dev), phy->dev_flags, PHY_INTERFACE_MODE_GMII);
if (speed == 0) {
phy->autoneg = AUTONEG_ENABLE;
--
1.8.1
next prev parent reply other threads:[~2013-01-10 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 12:00 Fix phy_init for Marvell network eth driver Kosta Zertsekel
2013-01-10 12:00 ` Kosta Zertsekel [this message]
2013-01-10 13:22 ` [PATCH 1/2] " Sergei Shtylyov
2013-01-10 12:00 ` [PATCH 2/2] Fix phy_attach - forward dev_flags for phy_attach Kosta Zertsekel
2013-01-10 14:40 ` Florian Fainelli
2013-01-10 15:57 ` Kosta Zertsekel
2013-01-10 17:12 ` Florian Fainelli
2013-01-10 12:17 ` Fix phy_init for Marvell network eth driver Jason Cooper
2013-01-10 12:24 ` Andrew Lunn
2013-01-10 12:27 ` Kosta Zertsekel
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=1357819234-27752-2-git-send-email-konszert@marvell.com \
--to=konszert@marvell.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=benavi@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=zertsekel@gmail.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;
as well as URLs for NNTP newsgroup(s).