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] smc91111: add fixup for qemu phy support
Date: Fri, 20 Sep 2013 08:50:45 +0200 [thread overview]
Message-ID: <20130920065045.GZ30088@pengutronix.de> (raw)
In-Reply-To: <1379590873-32588-1-git-send-email-plagnioj@jcrosoft.com>
On Thu, Sep 19, 2013 at 01:41:13PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> as today qemu does not support phy, it will return always 0x0 to any read
> on the mii bus. So the phy_id is 0 and the link is donw.
>
> To have the norwork running on versatilpb & other qenu board for the link up
> at 100Mbps.
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> ---
> drivers/net/smc91111.c | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/smc91111.c b/drivers/net/smc91111.c
> index 48183dd..8c7a343 100644
> --- a/drivers/net/smc91111.c
> +++ b/drivers/net/smc91111.c
> @@ -886,6 +886,7 @@ static void smc91c111_enable(struct eth_device *edev)
> static int smc91c111_eth_open(struct eth_device *edev)
> {
> struct smc91c111_priv *priv = (struct smc91c111_priv *)edev->priv;
> + int ret;
>
> /* Configure the Receive/Phy Control register */
> SMC_SELECT_BANK(priv, 0);
> @@ -893,8 +894,27 @@ static int smc91c111_eth_open(struct eth_device *edev)
>
> smc91c111_enable(edev);
>
> - return phy_device_connect(edev, &priv->miibus, 0, NULL,
> + ret = phy_device_connect(edev, &priv->miibus, 0, NULL,
> 0, PHY_INTERFACE_MODE_NA);
> +
> + if (ret)
> + return ret;
> +
> + if (edev->phydev->phy_id == 0x00000000) {
Can we make this test more explicit by adding a flag to platform_data?
Normally reading 0x0 from a phy means something is really wrong. Just
assuming everything is fine since it might be qemu is imo not good,
> +
> + dev_info(edev->parent, "phy with id 0x%08x detected this might be qemu\n",
> + dev->phy_id);
even if there's a warning message.
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
prev parent reply other threads:[~2013-09-20 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 11:41 Jean-Christophe PLAGNIOL-VILLARD
2013-09-20 6:50 ` 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=20130920065045.GZ30088@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