From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: afleming@freescale.com, linuxppc-dev@lists.ozlabs.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] mpc836x: fix failed phy detection for ucc ethernet on MDS
Date: Fri, 16 Mar 2012 14:36:33 -0500 [thread overview]
Message-ID: <329E382B-6DB2-4AC0-BC79-59296633FE9E@kernel.crashing.org> (raw)
In-Reply-To: <1330345501-24949-1-git-send-email-paul.gortmaker@windriver.com>
On Feb 27, 2012, at 6:25 AM, Paul Gortmaker wrote:
> The mpc836x_mds platform has been broken since the commit
> 6fe3264945ee63292cdfb27b6e95bc52c603bb09
>
> "netdev/phy: Use mdiobus_read() so that proper locks are taken"
>
> which caused the fsl_pq_mdio TBI autoprobe to oops. The oops
> was "fixed" in commit 28d8ea2d568534026ccda3e8936f5ea1e04a86a1
>
> "fsl_pq_mdio: Clean up tbi address configuration"
>
> by simply removing the the autoscan code, and making tbi nodes
> mandatory. Some of the newer reference platforms were updated
> to have tbi nodes in 220669495bf8b68130a8218607147c7b74c28d2b
>
> "powerpc: Add TBI PHY node to first MDIO bus"
>
> but the older mpc836x didn't get one and hence was just failing
> with -EBUSY as follows:
>
> fsl-pq_mdio: probe of e0102120.mdio failed with error -16
> ...
> net eth0: Could not attach to PHY
> eth0: Cannot initialize PHY, aborting.
>
> Add a TBI node and use the 1st free address for it.
>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
applied
- k
prev parent reply other threads:[~2012-03-16 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 12:25 [PATCH] mpc836x: fix failed phy detection for ucc ethernet on MDS Paul Gortmaker
2012-03-01 22:06 ` Andy Fleming
2012-03-16 19:36 ` Kumar Gala [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=329E382B-6DB2-4AC0-BC79-59296633FE9E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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