From: Petr Kulhavy <petr@barix.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: davinci-mdio: failing to connect to PHY
Date: Mon, 4 Apr 2016 16:01:28 +0200 [thread overview]
Message-ID: <570273B8.1030205@barix.com> (raw)
In-Reply-To: <20160404135813.GA25131@lunn.ch>
On 04.04.2016 15:58, Andrew Lunn wrote:
> On Mon, Apr 04, 2016 at 03:50:02PM +0200, Petr Kulhavy wrote:
>> Hi Andrew,
>>
>> thanks a lot for the link. In the meantime I've understood the issue
>> better. It is due to the fact that the PHY is pin-strapped to
>> address 1 and broadcast (at address 0) is enabled. The Micrel
>> driver's config_init() disables the broadcast and the PHY stops
>> responding, which causes the troubles. The kernel 3.17 didn't
>> disable the broadcast and therefore it worked.
>>
>> I'm wondering how to solve or workaround this...
> One option is in your device tree is to explicitly list the phy on
> your mdio bus. Something like:
>
> &mdio {
> status = "okay";
>
> ethphy0: ethernet-phy@1 {
> reg = <1>;
> };
> };
>
> This alone might be sufficient. If not, you need to reference the phy
> via a phandle in the ethernet node.
>
>
> ð0 {
> status = "okay";
> phy-handle = <ðphy0>;
> };
>
> Andrew
Thanks a lot, I'm going to try it out right now!
Cheers
Petr
next prev parent reply other threads:[~2016-04-04 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:18 davinci-mdio: failing to connect to PHY Petr Kulhavy
2016-04-04 12:31 ` Andrew Lunn
2016-04-04 13:50 ` Petr Kulhavy
2016-04-04 13:58 ` Andrew Lunn
2016-04-04 14:01 ` Petr Kulhavy [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-01 15:24 Petr Kulhavy
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=570273B8.1030205@barix.com \
--to=petr@barix.com \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.