From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Sascha Hauer <sha@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: RE: [PATCH 2/2] ARM: Layerscape: Add LS1021A IOT board support
Date: Fri, 17 Feb 2023 15:22:04 +0000 [thread overview]
Message-ID: <BL0PR07MB5665BD8EF62784E9C8017142ECA19@BL0PR07MB5665.namprd07.prod.outlook.com> (raw)
In-Reply-To: <20230217093619.GP10447@pengutronix.de>
> Indeed,
> > barebox@LS1021A-IOT Board:/ miitool -v
> > mdio0-phy00: 2d24000.mdio@2d24000.of: no link
> > product info: Generic PHY (vendor 00:00:00, model 0 rev 0)
> > basic mode: autonegotiation enabled
> > basic status: no link
> > capabilities:
> > advertising:
> > mdio0-phy01: 2d24000.mdio@2d24000.of: negotiated 100baseTx-FD, link
> ok
> > product info: Generic PHY (vendor 00:13:74, model 7 rev 4)
> > basic mode: autonegotiation enabled
> > basic status: autonegotiation complete, link ok
> > capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> > advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> > link partner: 1000baseT-FD 1000baseT-HD 100baseTx-FD 100baseTx-HD
> > 10baseT-FD 10baseT-HD flow-control
> > mdio0-phy03: 2d24000.mdio@2d24000.of: negotiated 100baseTx-FD, link
> ok
> > product info: Generic PHY (vendor 00:13:74, model 7 rev 4)
> > basic mode: autonegotiation enabled
> > basic status: autonegotiation complete, link ok
> > capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> > advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
> > link partner: 1000baseT-FD 1000baseT-HD 100baseTx-FD 100baseTx-HD
> > 10baseT-FD 10baseT-HD flow-control
>
> I have no idea what goes wrong here.
>
> Some things to dig further:
>
> A phy is registered in phy_register_device(). The call to register_device() in
> that function will end up in mdio_bus_match(). You could add some
> debugging there to see which phy ids are matched against each other.
>
> An idea is that the at803x driver is not yet registered by the time
> phy_device_connect() is called, but I don't see how this could happen.
Ok. I have registered the mdio driver from the Ethernet device probe function with platform_driver_register (like the ls1046a).
Now the Atheros driver isregistered first prior to probing the mdiobus. I got a crash but I shall figure out.
Thanks.
next prev parent reply other threads:[~2023-02-17 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 13:26 Renaud Barbier
2023-02-10 12:23 ` Sascha Hauer
2023-02-16 11:54 ` Renaud Barbier
2023-02-16 12:54 ` Sascha Hauer
2023-02-16 13:56 ` Renaud Barbier
2023-02-17 9:36 ` Sascha Hauer
2023-02-17 13:44 ` Renaud Barbier
2023-02-17 14:51 ` Sascha Hauer
2023-02-17 18:06 ` Renaud Barbier
2023-02-21 10:31 ` Sascha Hauer
2023-02-17 15:22 ` Renaud Barbier [this message]
2023-02-16 13:58 ` Renaud Barbier
2023-03-13 14:43 Renaud Barbier
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=BL0PR07MB5665BD8EF62784E9C8017142ECA19@BL0PR07MB5665.namprd07.prod.outlook.com \
--to=renaud.barbier@ametek.com \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/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