<smaeul>
there are at least three tries at a second-generation PWM controller driver: two on the list plus Sipeed/MoeIcenowy's R329 mainline kernel fork
<smaeul>
T113 CPU power switches should be similar to other Cortex-A7 chips
rajkosto has joined #linux-sunxi
apritzel has joined #linux-sunxi
anarsoul has joined #linux-sunxi
anarsoul has quit [Remote host closed the connection]
<apritzel>
I think jernej (and others) have more experience with the OPi3 LTS, which is a bit of a special snowflake
<warpme>
ah ok - will ask jernej on LE slack. thx!
<apritzel>
warpme: did you compile TF-A with SUNXI_SETUP_REGULATORS=0? AFAIK this is needed for the Ethernet PHY sequencing to work
<warpme>
apritzel : if you are referring to getting int.phy working on h313/h616 then no. I'm not using this at atf compile. I have working int.eth on h313/h616 (with auto.detect of ac200/ac300) by devel some patches atop of old v2021.07 uboot :-(
<apritzel>
No, I am talking about that the TF-A regulator setup code upsets the PHY used on the OrangePi 3 (LTS?) board, because that needs special sequencing, which the TF-A code does not provide
<warpme>
ah well. ok. may you be a bit more specific when saying "upsets the PHY"?
<apritzel>
the solution is to let TF-A skip that AXP setup (that code should go away anyway), at the cost of losing Ethernet support in U-Boot, at least for now
<apritzel>
read the comment in the DT: it needs the different power rails to come up in a specific sequence, with specific delays, otherwise it won't work
<warpme>
indeed. but this is about GE Eth which works well for me....
<apritzel>
no, that clock looks unrelated, I was just wondering if the wrong PHY setup sequence spoils your Ethernet performance
<warpme>
Eth seems work well with avg speed 911Gbps throughput
<warpme>
i'm a bit lost why i'm getting sun50i-h6-r-pinctrl 7022000.pinctrl: pin-387 (7022000.pinctrl:387) status -517 on WIFI_PWR_ON gpio?
<apritzel>
-517 means deferred, so the WiFi power sequence probes before the R_PIO pinctrl. That message is probably a red herring, because it resolves itself later, check /sys/kernel/debug/devices_deferred
<apritzel>
(those EPROBE_DEFER error codes shouldn't actually be reported, feel free to send a patch)
<warpme>
that was my idea but /sys/kernel/debug/devices_deferred has zero entries...
<apritzel>
then it's all good, and you can ignore this message (another hint it should be removed)
<apritzel>
looking again this error message actually comes from the pinctrl driver, so there is something else at play, but since you don't have anything in devices_deferred, it's still good, I guess
grming has joined #linux-sunxi
cnxsoft has quit []
rajkosto has quit [Quit: Leaving]
grming has quit [Quit: Konversation terminated!]
warpme has quit []
evgeny_boger1 has joined #linux-sunxi
evgeny_boger1 has quit [Remote host closed the connection]
sunshavi has joined #linux-sunxi
evgeny_boger has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
warpme has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
cnxsoft has quit []
bauen1 has quit [Remote host closed the connection]
bauen1 has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
hentai has joined #linux-sunxi
<apritzel>
smaeul: thanks for the pointer to MoeIcenowy's PWM driver, so much choice ;-) From a first glance at the copyright it looks it's based on one of the earlier ones
<apritzel>
but that driver is not very high on my list at the moment, anyway ...
<apritzel>
smaeul: for the T113s: I found it's actually closer to the NCAT2 cores