Hi Vladimir, On Sat, Jul 13, 2019 at 5:44 PM Vladimir Oltean <[email protected]> wrote: > > Hi Bin, > > On Sat, 13 Jul 2019 at 07:55, Bin Meng <[email protected]> wrote: > > > > Hi Vladimir, > > > > On Mon, Jun 24, 2019 at 1:50 AM Vladimir Oltean <[email protected]> wrote: > > > > > > By convention, the eTSEC MDIO controller nodes are defined in DT at > > > 0x2d24000 and 0x2d50000, but actually U-boot does not touch the > > > > nits: U-Boot, not U-boot > > > > > interrupt portion of the register map (MDIO_IEVENTM, MDIO_IMASKM, > > > MDIO_EMAPM). > > > > > > That leaves only the MDIO bus registers (MDIO_MIIMCFG, MDIO_MIIMCOM, > > > MDIO_MIIMADD, MDIO_MIIMADD, MDIO_MIIMCON, MDIO_MIIMSTAT) which start at > > > the 0x520 offset. > > > > > > So shift the DT-defined register map by the offset of MDIO_MIIMCFG when > > > mapping the MDIO bus registers. > > > > Could you please create a TSEC MDIO DM driver based on this series > > that Alex has done? > > > > http://patchwork.ozlabs.org/project/uboot/list/?series=111504? > > > > Yes I actually said in the cover letter that I want to do that, but it > has to get merged first :)
That's good to know :) Regards, Bin _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
