[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJq09z7QMvcW6eiY7OcmpxXiNMpd5h+2v+tH_YMeGsL2qRr7nQ@mail.gmail.com>
Date: Fri, 31 Dec 2021 00:10:51 -0300
From: Luiz Angelo Daros de Luca <luizluca@...il.com>
To: Alvin Šipraga <ALSI@...g-olufsen.dk>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"vivien.didelot@...il.com" <vivien.didelot@...il.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"olteanv@...il.com" <olteanv@...il.com>,
"arinc.unal@...nc9.com" <arinc.unal@...nc9.com>
Subject: Re: [PATCH net-next v2 07/13] net: dsa: realtek: add new mdio
interface for drivers
> > + /* Write Start command to register 29 */
> > + bus->write(bus, phy_id, MDC_MDIO_START_REG, MDC_MDIO_START_OP);
>
> I'm curious where these START commands came from because I cannot find
> an anlogous procedure in the Realtek driver dump I have. Did you figure
> this out empirically? Does it not work without? Same goes for the other
> ones downstairs.
It works without the MDC_MDIO_START_REG. I'm also curious that it
really does. It is present in uboot driver and OpenWrt driver. That
MDC_MDIO_START_REG is even defined in Realtek rtl8637c, but not used.
I think it might be something that an old family (rtl8637b) required
but not newer ones.
I'll drop it.
Powered by blists - more mailing lists