From: Heiner Kallweit <hkallweit1@gmail.com>
To: Ron Eggler <ron.eggler@mistywest.com>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: issues to bring up two VSC8531 PHYs
Date: Thu, 13 Apr 2023 00:12:28 +0200 [thread overview]
Message-ID: <bb62e044-034e-771e-e3a9-a4b274e3dec9@gmail.com> (raw)
In-Reply-To: <5eb810d7-6765-4de5-4eb0-ad0972bf640d@mistywest.com>
On 12.04.2023 22:11, Ron Eggler wrote:
> Hi,
> I am trying to bring up a pair of VSC9531 PHYs on an embedded system. I'm using a Yocto build and have altered the device tree with the following patch:
> https://github.com/MistySOM/meta-mistysom/blob/phy-enable/recipes-kernel/linux/smarc-rzg2l/0001-add-vsc8531-userspace-dts.patch
> I installed mdio-tools and can see the interfaces like:
> # mdio
> 11c20000.ethernet-ffffffff
> 11c30000.ethernet-ffffffff
>
> Also, I hooked up a logic analyzer to the mdio lines and can see communications happening at boot time. Also, it appears that it's able to read the link status correctly (when a cable is plugged):
> # mdio 11c20000.ethernet-ffffffff
> DEV PHY-ID LINK
> 0x00 0x00070572 up
>
AFAICS there's no PHY driver yet for this model. The generic driver may or may not work.
Best add a PHY driver.
> Yet, ifconfig doesn't show the interfaces and I get:
> # ifconfig eth0 up
> [ 140.542939] ravb 11c20000.ethernet eth0: failed to connect PHY
> SIOCSIFFLAGS: No such file or directory
> When I try to bring it up
>
> # ip l displays the interfaces as:
> 4: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ether 9a:ab:83:16:65:36 brd ff:ff:ff:ff:ff:ff
> 5: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ether 2a:9d:bf:09:8d:c3 brd ff:ff:ff:ff:ff:ff
>
> Where am I going from here? I have experimented with drilling down into bitwise analysis of the MDIO communications. I'm uncertain though if this is my best bet, does someone here have any insight and can provide me with some guidance?
>
Any specific reason why you set the compatible to ethernet-phy-ieee802.3-c45 for a c22 PHY?
> Thanks a lot!
It would be advisable to include the phylib maintainers when asking phylib-related questions.
next prev parent reply other threads:[~2023-04-12 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 20:11 issues to bring up two VSC8531 PHYs Ron Eggler
2023-04-12 22:10 ` Andrew Lunn
2023-04-12 22:12 ` Heiner Kallweit [this message]
2023-04-12 22:20 ` Andrew Lunn
2023-04-12 22:37 ` Heiner Kallweit
2023-04-13 20:13 ` Ron Eggler
2023-04-13 20:27 ` Andrew Lunn
2023-04-21 16:06 ` Ron Eggler
2023-04-21 16:35 ` Andrew Lunn
2023-04-21 22:55 ` Ron Eggler
2023-04-22 0:09 ` Florian Fainelli
2023-04-23 22:53 ` Ron Eggler
2023-04-22 0:28 ` Ron Eggler
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=bb62e044-034e-771e-e3a9-a4b274e3dec9@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=ron.eggler@mistywest.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