ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #linux-rockchip
kevery has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
kevery has quit [Remote host closed the connection]
kevery1 has joined #linux-rockchip
kevery1 is now known as kevery
arnd has quit [Ping timeout: 240 seconds]
arnd has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-rockchip
lurchi_ is now known as lurchi__
_whitelogger has joined #linux-rockchip
hl has quit [*.net *.split]
lkcl has quit [*.net *.split]
jelly has quit [*.net *.split]
rtp has quit [*.net *.split]
UndrWater has quit [*.net *.split]
rtp has joined #linux-rockchip
UndrWater has joined #linux-rockchip
hl has joined #linux-rockchip
lkcl has joined #linux-rockchip
jelly has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
tomeu has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
archetyp has joined #linux-rockchip
kevery has quit [Quit: kevery]
alpernebbi has joined #linux-rockchip
punit_ is now known as punit
alpernebbi has quit [Quit: alpernebbi]
<punit> It looks like 5.14 broke ethernet on RockPro64 - bisection points to 2d26f6e39afb ("net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings")
<punit> The ethernet device shows up but DHCP fails. Manually setting the address doesn't help either
<punit> Anybody else see this failure?
<mriesch> hi punit. thanks for your mail.
<mriesch> punit: as i already said, i do not have any rk3399 hardware at the moment, but if i can help somehow anyway let me know :-)
<mriesch> does the rk3399 have an integrated phy/is it used on the rockpro64?
robmur01_ has joined #linux-rockchip
archetyp has quit [Quit: Leaving]
robmur01 has quit [Ping timeout: 250 seconds]
archetyp has joined #linux-rockchip
<mriesch> ok, it seems the rockpro64 features an external phy. but shouldn't the gmac node expose a mdio property in this case?
chewitt has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
warpme_ has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 240 seconds]
vagrantc has joined #linux-rockchip
lurchi__ is now known as lurchi_
cp- has quit [Read error: Connection reset by peer]
lurchi_ has quit [Ping timeout: 240 seconds]
lurchi__ has joined #linux-rockchip
<pgwipeout[m]> Hmmm, you're right. I'm going to have some fun here.
<punit> mriesch: Thanks! Not sure about the mdio property being needed.
<punit> I see the following in dmesg -
<punit> [ +0.005760] mdio_bus stmmac-0:00: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
<punit> [ +0.006159] mdio_bus stmmac-0:01: attached PHY driver [unbound] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
<punit> [ +0.613770] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [Generic PHY] (irq=POLL)
<punit> also, there is no difference in the logs with and without your patch.