From: Angelo Dureghello <angelo70@gmail.com>
To: Bruno Thomsen <bth@kamstrup.dk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Micrel KSZ8031 - phy link missing
Date: Fri, 10 Oct 2014 14:54:18 +0200 [thread overview]
Message-ID: <5437D6FA.9070304@gmail.com> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D0163C7A7F9@Exchange2010.kamstrup.dk>
Dear Bruno,
i added the fixup, nothing changes.
I am tracing flags at ksz8021_config_ini:
Starting network...
davinci_mdio davinci_mdio.0: resetting idled controller
micrel.c: ksz8021_config_init: flags: 0x00000203
net eth0: attached PHY driver [Micrel KSZ8031]
(mii_bus:phy_addr=davinci_mdio-0:00, id=221556)
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
So, MICREL_PHY_50MHZ_CLK seems to be set.
I have the suspect that the clock is not received from the phy.
Unfortunately i can't check
with the scope, the micrel chip is on a hidden part of the board.
From what i remember, when i was trying to init emac/phy by devicetree,
it was working.
[root@barix ~]# cat /sys/class/net/eth0/carrier
0
[root@barix ~]# cat /sys/class/net/eth0/carrier_changes
1
[root@barix ~]#
I realize at this point is my own debugging / issue.
But if you have any idea how to debug this, i can put some traces here
and there.
Still many thanks,
Angelo
On 10/10/2014 13:32, Bruno Thomsen wrote:
> Hey again,
> Looks like you just enable clock output from DA850. You also need to setup PHY to accept RMII clock from MAC.
> This can be done with something like this...
>
> ...
>
>
next prev parent reply other threads:[~2014-10-10 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 15:05 Micrel KSZ8031 - phy link missing Bruno Thomsen
2014-10-10 9:32 ` Angelo Dureghello
2014-10-10 10:31 ` Bruno Thomsen
2014-10-10 10:54 ` Angelo Dureghello
2014-10-10 11:32 ` Bruno Thomsen
2014-10-10 12:54 ` Angelo Dureghello [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 18:28 Angelo Dureghello
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=5437D6FA.9070304@gmail.com \
--to=angelo70@gmail.com \
--cc=bth@kamstrup.dk \
--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 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).