From: Andrew Lunn <andrew@lunn.ch>
To: netdev@vger.kernel.org, fugang.duan@nxp.com
Subject: Re: fec driver and two micrel phys
Date: Tue, 28 Nov 2017 17:09:06 +0100 [thread overview]
Message-ID: <20171128160906.GD14512@lunn.ch> (raw)
In-Reply-To: <20171128152815.GB32345@graute-opti>
On Tue, Nov 28, 2017 at 04:28:15PM +0100, Oliver Graute wrote:
> Hello list,
>
> I try to get two Micrel KSZ8041 Phys working with the fec driver from
> Kernel 4.14. But it looks that something with the mii_bus probing is not
> working here. I expect the Phys on address 01 and 03. Currently on eth1
> I see TX traffic but no RX. On eth0 there is neither nor. (ifconfig)
>
> [ 51.997034] Micrel KSZ8041 800f0000.ethernet-1:00: attached PHY driver [Micrel KSZ8041] (mii_bus:phy_addr=800f0000.ethernet-1:00, irq=POLL)
> [ 52.036719] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 52.621138] Micrel KSZ8041 800f0000.ethernet-1:01: attached PHY driver [Micrel KSZ8041] (mii_bus:phy_addr=800f0000.ethernet-1:01, irq=POLL)
> [ 52.649677] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 54.697479] fec 800f4000.ethernet eth1: Link is Up - 100Mbps/Full - flow control off
> [ 54.721424] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> [ 59.860693] Micrel KSZ8041 800f0000.ethernet-1:00: attached PHY driver [Micrel KSZ8041] (mii_bus:phy_addr=800f0000.ethernet-1:00, irq=POLL)
> [ 59.874298] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 59.980688] Micrel KSZ8041 800f0000.ethernet-1:01: attached PHY driver [Micrel KSZ8041] (mii_bus:phy_addr=800f0000.ethernet-1:01, irq=POLL)
> [ 59.994289] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 62.025331] fec 800f4000.ethernet eth1: Link is Up - 100Mbps/Full - flow control off
> [ 62.044588] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
>
>
> On my old setup with an Kernel 4.2 the phys are working. But there I
> patched the phy_mask into the old fec code. Because I didn't know how to
> do it better by device tree.
>
> Can someone tell my how to do it right?
Hi Oliver
Can you show use your device tree? You should be using phy-handle to
point to the PHYs on the MDIO bus.
Andrew
next prev parent reply other threads:[~2017-11-28 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 15:28 fec driver and two micrel phys Oliver Graute
2017-11-28 16:09 ` Andrew Lunn [this message]
2017-11-29 7:29 ` Oliver Graute
2017-11-29 9:08 ` Oliver Graute
2017-11-29 16:12 ` Andrew Lunn
2017-11-29 1:38 ` Andy Duan
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=20171128160906.GD14512@lunn.ch \
--to=andrew@lunn.ch \
--cc=fugang.duan@nxp.com \
--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).