ikarso has quit [Quit: Connection closed for inactivity]
<calebccff>
does anyone else occasionally bump into "WARN endpoint is halted" failures in dwc3? it usually doesn't happen on the first access but some time afterwards
dsimic has quit [Ping timeout: 255 seconds]
<marex>
calebccff: someone should really sync the DWC3 driver with Linux properly
<marex>
calebccff: if you have time to do it, it would be most welcome
<marex>
calebccff: I already explained to Xilinx how to do it like 5 times ...
<calebccff>
heh, i was worried you'd say that :P
<calebccff>
I'd be happy to have a crack at it, probably wouldn't be for at least another few weeks though
dsimic has joined #u-boot
<marex>
calebccff: basically figure out which commit in Linux was the dwc3 driver pulled from, revert all U-Boot patches on dwc3 since, cherry-pick the Linux patches on top, git rebase -i ... drop the reverts, let git resolve the rest
<marex>
calebccff: it should be relatively mechanical task
<calebccff>
marex: iirc it was last sync'd from 3.x
<LeSpocky>
o.O
prabhakarlad has quit [Ping timeout: 250 seconds]
<calebccff>
3.19-rc1
<marex>
calebccff: if you revert all the changes on top, you should get that state of the code base, so the Linux patches should apply cleanly
<calebccff>
riight yeah, im sure it being so easy is why nobody else has done it in the last... 9 years ;)
<marex>
calebccff: you can look up the xilinx threads ... they didn't even try
sng has joined #u-boot
<marex>
calebccff: I asked multiple times whether there is any issue with this method, never got any feedback, so I gave up
mmu_man has joined #u-boot
prabhakar has quit [Ping timeout: 240 seconds]
KREYREN has quit [Ping timeout: 260 seconds]
KREYREN has joined #u-boot
prabhakalad has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
ladis has quit [Quit: Leaving]
ikarso has joined #u-boot
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
KREYREN has quit [Ping timeout: 260 seconds]
KREYREN has joined #u-boot
stefanro has quit [Ping timeout: 255 seconds]
enok has quit [Ping timeout: 246 seconds]
zsoltiv_ has joined #u-boot
Stat_headcrabed has joined #u-boot
stefanro has joined #u-boot
slobodan__ has quit [Read error: Connection reset by peer]
<austriancoder>
is it possible to runtime-patch u-boots own dtb?
slobodan__ has joined #u-boot
<austriancoder>
in spl
<marex>
austriancoder: in SPL for SPL or in SPL for U-Boot proper ?
<austriancoder>
n SPL for U-Boot proper
<marex>
yeah, do you want it via DTO or via fiddling with DT ?
<marex>
fiddling with DT -- ef7ceb3ec7bd ("arm64: imx8mp: Auto-detect PHY on i.MX8MP DHCOM")
<marex>
DTO of the same -- ad1158c50e0e ("arm64: dts: imx8mp: Switch to DT overlays for i.MX8MP DHCOM SoM")
<austriancoder>
marex: thanks - I will go route #1 aka fiddling with DT
<marex>
austriancoder: that starts to be painful very soon btw , if the change is small, sure, once the change is larger it is a major pain in the uh ... backend
<marex>
32a41b7c3783 ("ARM: imx: Auto-detect PHY on Data Modul i.MX8M Mini/Plus eDM SBC")
<marex>
had something similar recently
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #u-boot
rfs613 has quit [Ping timeout: 264 seconds]
<austriancoder>
thx
rfs613 has joined #u-boot
<austriancoder>
marex: one problem I see is doing an mdio scan in SPL -> fec net driver needs to be in SPL .. hmm
<marex>
austriancoder: can you discern the boards in some other way ?
<marex>
austriancoder: in my case, it was a pull up/down resistor
<austriancoder>
marex: need to ask the person from solidrun
<marex>
austriancoder: do you have both machines ?
<marex>
austriancoder: how did it work before ?
vagrantc has joined #u-boot
<austriancoder>
I ma not sure if I have both types.. I have around 8 of these devices and need to check. One note from the mail that makes it harder even if there is a resistor: i.MX6 SoMs originally had a an atheros phy at unstable address, either 0 or 4 depending on electrical noise on floating configuration signals
<austriancoder>
marex: the problem came via a device-tree sync where the new som phy was added
<marex>
urgh
<marex>
austriancoder: could you set those configuration signals from the MX6 and then toggle the PHY reset , to force correct PHY address ?
<austriancoder>
marex: that could work
rvalue has joined #u-boot
enok has joined #u-boot
rvalue has quit [Ping timeout: 256 seconds]
lixkel_ has quit [Quit: Lost terminal]
rvalue has joined #u-boot
rvalue has quit [Ping timeout: 255 seconds]
rvalue has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 252 seconds]
rvalue- is now known as rvalue
cbmuser has quit [Ping timeout: 246 seconds]
rvalue has quit [Ping timeout: 268 seconds]
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
stefanro has quit [Quit: Leaving.]
rvalue has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 264 seconds]
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
rvalue- is now known as rvalue
Stat_headcrabed has quit [Quit: Stat_headcrabed]
cbmuser has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 260 seconds]
tgamblin has quit [Quit: Leaving]
<austriancoder>
marex: There is no cpu control over the signals responsible for phy address :(
<austriancoder>
could it be done in U-Boot proper only?
<austriancoder>
and there are no resistors etc to get this info - so only mdio scanning
rvalue- is now known as rvalue
mmu_man has quit [Ping timeout: 256 seconds]
Clamor has quit [Ping timeout: 255 seconds]
rvalue has quit [Ping timeout: 268 seconds]
<marex>
austriancoder: dang
Clamor has joined #u-boot
<marex>
austriancoder: do you know which one is floating ? RXD0/RXD1/LED_ACT ?
<marex>
I guess LED_ACT, right ?
<marex>
austriancoder: I wonder if you could do something creative in board_phy_config() in U-Boot proper, like try to communicate with PHY at address 0x0 , if it fails, try 0x4
<marex>
oh wait ...
<marex>
wait a minute ...
rvalue has joined #u-boot
<marex>
austriancoder: board/solidrun/mx6cuboxi/mx6cuboxi.c already contains find_ethernet_phy() which does phy_find_by_mask()
<marex>
austriancoder: isnt that supposed to deal with your PHY problem ?
<marex>
but maybe that is only for linux DT
<marex>
but I wonder, if something like phy_find_by_mask() could also be wired into board_phy_config() to do the same for U-Boot PHY handling, I think that should do the trick
<austriancoder>
I will ask which one is floating. Yeah find_ethernet_phy() is used to patch linux DT. board_phy_config() .. will try that trick
rvalue has quit [Ping timeout: 272 seconds]
rvalue has joined #u-boot
monstr has quit [Remote host closed the connection]
KREYREN has quit [Remote host closed the connection]
KREYREN has joined #u-boot
rvalue has quit [Ping timeout: 264 seconds]
jfsimon1981 has joined #u-boot
<marex>
austriancoder: ah ... hah
<marex>
austriancoder: can you try ...
<marex>
austriancoder: look at drivers/net/fec_mxc.c and search around fec_phy_init() for CFG_FEC_MXC_PHYADDR
<marex>
austriancoder: that's where the PHY is bound to the MAC , and where the PHY address look up happens
<marex>
that is where you might want some of this phy_find_by_mask I think