04:40 <naoki> hmmm... ethernet phy compatible like "ethernet-phy-id001c.c916"; should be defined? I checked several dts, but only some boards defined it

06:39 <dsimic> naoki: what did you actually mean with the comparison between rk3399-rock-pi-4.dtsi and rk3399-rock-4se.dts?

06:43 <dsimic> regarding ethernet-phy-id001c.c916, have a look at function fwnode_get_phy_id() in drivers/net/phy/phy_device.c

07:02 <Kwiboo> if the phy-id and mdio addr is known and static for the lifetime a board model an ethernet-phy-id compatible and reg=<phyad> can probably be used instead of a ethernet-phy-ieee802.3-c22 compatible (with/without reg=0)

07:04 <Kwiboo> with ethernet-phy-id001c.c916 compatible for a board with rtl8211f the ethernet phy reset done in u-boot may not be needed and linux may be successful in resetting the phy before use

07:07 <Kwiboo> i.e. the phy device is created before phy-id is initially read and the chicken-and-egg problem per https://lore.kernel.org/all/47d55aca-bee6-810f-379f-9431649fefa6@kwiboo.se/ is worked around

08:37 <naoki> dsimic: 4se.dts includes pi-4.dtsi. common thing can be remove from 4se.dts

08:47 <naoki> Kwiboo: thanks. there are ROCK Pi E which uses rtl8211e and rtl8211f, so we can't use ethernet-phy-id...

08:48 <hrw> naoki: but those rtl8211 are on pcie bus, right? so should not have to be in DT imho

08:50 <naoki> hrw: no pci

08:50 <hrw> ah, ok

08:54 <naoki> (... -pi-e.dts, -pi-e-v121.dts, -pi-e-v3.dts ...)