On Thu, Aug 1, 2019 at 4:32 AM Patrick Delaunay wrote:
>
> Align the board and driver prototype for board_interface_eth_init
> to avoid execution issue (the interface_type parameter is defined
> as int or phy_interface_t).
>
> To have a generic weak function (it should be reused by other driver)
Hi Ramon,
No need to write specific phy driver, uboot phy generic driver is working
fine.
The goal of board_interface_eth_init function is only to configure syscfg
register with good value in function of interface type (MII, RMII, GMII
...). And this syscfg value is specific for each platform.
On Thu, Aug 1, 2019 at 12:32 PM Patrick Delaunay
wrote:
>
> Align the board and driver prototype for board_interface_eth_init
> to avoid execution issue (the interface_type parameter is defined
> as int or phy_interface_t).
>
> To have a generic weak function (it should be reused by other driver)
Align the board and driver prototype for board_interface_eth_init
to avoid execution issue (the interface_type parameter is defined
as int or phy_interface_t).
To have a generic weak function (it should be reused by other driver)
I change the prototype to use directly udevice.
This prototype is
4 matches
Mail list logo