* phy driver @ 2021-12-07 18:51 Barbier, Renaud 2021-12-08 9:30 ` Barbier, Renaud 0 siblings, 1 reply; 2+ messages in thread From: Barbier, Renaud @ 2021-12-07 18:51 UTC (permalink / raw) To: Barebox List I am working on a LS1021A currently booting from SPI NOR. I am having difficulties to get the network port working. Issue is that the PHY AR8033 is not initialized properly and even though I get the correct speed/duplex at first (1000FD), no data go through. Clearing/writing 0x100 to the phy control register then gives the lowest speed/duplex(10HD) and ping works. The at803.c phy driver is now enabled but I do not see the driver probe function being called and neither mdio_bus_match. I see a few examples of device trees to add the properties found in the driver. What else am I missing for the at803 to be used. Cheers, Renaud _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: phy driver 2021-12-07 18:51 phy driver Barbier, Renaud @ 2021-12-08 9:30 ` Barbier, Renaud 0 siblings, 0 replies; 2+ messages in thread From: Barbier, Renaud @ 2021-12-08 9:30 UTC (permalink / raw) To: Barbier, Renaud, Barebox List I found a few boards support that fixup. It is likely it will work for the LS1021 AR8033 -----Original Message----- From: barebox <barebox-bounces@lists.infradead.org> On Behalf Of Barbier, Renaud Sent: 07 December 2021 18:51 To: Barebox List <barebox@lists.infradead.org> Subject: phy driver [**EXTERNAL SOURCE**]:Please verify the source before clicking link or opening attachment. I am working on a LS1021A currently booting from SPI NOR. I am having difficulties to get the network port working. Issue is that the PHY AR8033 is not initialized properly and even though I get the correct speed/duplex at first (1000FD), no data go through. Clearing/writing 0x100 to the phy control register then gives the lowest speed/duplex(10HD) and ping works. The at803.c phy driver is now enabled but I do not see the driver probe function being called and neither mdio_bus_match. I see a few examples of device trees to add the properties found in the driver. What else am I missing for the at803 to be used. Cheers, Renaud _______________________________________________ barebox mailing list barebox@lists.infradead.org https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infradead.org%2Fmailman%2Flistinfo%2Fbarebox&data=04%7C01%7Crenaud.barbier%40abaco.com%7C06b9c64b270c4397a42108d9b9b2c183%7Ce6f27451899d4d0db8fa88baafa551a7%7C0%7C0%7C637744999676441621%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=OxSU%2BM3PvBjZKm4hJ9vK7Km%2Fjq2dLj3k%2BZUbLdsDv0Q%3D&reserved=0 _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-08 9:33 UTC | newest] Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-12-07 18:51 phy driver Barbier, Renaud 2021-12-08 9:30 ` Barbier, Renaud
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox