From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ron Eggler <ron.eggler@mistywest.com>,
netdev@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: issues to bring up two VSC8531 PHYs
Date: Thu, 13 Apr 2023 00:37:11 +0200 [thread overview]
Message-ID: <ba56f0a4-b8af-a478-7c1d-e6532144b820@gmail.com> (raw)
In-Reply-To: <46e4d167-5c96-41a0-8823-a6a97a9fa45f@lunn.ch>
On 13.04.2023 00:20, Andrew Lunn wrote:
>>> 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.
>
> Hi Heiner
>
> mscc.h:#define PHY_ID_VSC8531 0x00070570
>
> mscc_main.c:
OK, missed that. I just looked at the vitesse driver which also covers
a number of VSCxxxx PHY's.
> .phy_id = PHY_ID_VSC8531,
> .name = "Microsemi VSC8531",
> .phy_id_mask = 0xfffffff0,
> /* PHY_GBIT_FEATURES */
>
>> Any specific reason why you set the compatible to
>> ethernet-phy-ieee802.3-c45 for a c22 PHY?
>
> Ah, i missed that! The driver only uses phy_read/phy_write, not
> phy_write_mmd() and phy_read_mmd().
>
> Remove the compatible string. It is not needed for C22 PHYs.
>
> Andrew
next prev parent reply other threads:[~2023-04-12 22:37 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
2023-04-12 22:20 ` Andrew Lunn
2023-04-12 22:37 ` Heiner Kallweit [this message]
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=ba56f0a4-b8af-a478-7c1d-e6532144b820@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