<smaeul>
montjoie: in my very much WIP dissection of the H5 BROM at http://dpaste.com/196Z1VK, the mysterious code is func_2de8, which turns bits 0 & 1 of the undocumented register on and off in a loop. it's called several different times with different parameters. I assume it's some sort of debugging feature, meant to be detectable from outside the CPU
<montjoie>
smaeul: have you tried the datasheet/usermanual ?
2017-07-05
<mripard>
montjoie: thanks :)
<montjoie>
mripard: will send
2017-07-04
<mripard>
montjoie: can you send a patch to fix this ?
2017-07-02
<montjoie>
yes AC200 is a MFD
<montjoie>
facilities ?
<montjoie>
yes, just check PHY ID
<montjoie>
MoeIcenowy: yes AC200 seems to work with RGMII
<montjoie>
I have some hesitation to send a patch for hacing a new phy driver just to add "AC200" name
<montjoie>
on opipc it works as generic phy
<montjoie>
I got one
<montjoie>
I saw
<MoeIcenowy>
montjoie: I did a sun8i_emac on BPi M3 U-Boot
<luoyi>
montjoie: yes, but I can't find the wip repo. so I just modify codekipper's branch and get a working one
<montjoie>
MoeIcenowy: oh yeah when you said broken, its really broken:)
<montjoie>
I love to see my automatic toolchain building all
<montjoie>
updating ...
<montjoie>
still on 0602
<MoeIcenowy>
montjoie: the 24MHz xtal patch?
<montjoie>
MoeIcenowy: do you want me to send the patch (or you in a v3s support serie)
<montjoie>
right ?
<montjoie>
and since all known boards/soc use it... it is simplier to allways enable it
<montjoie>
MoeIcenowy: If I understand well, the default syscon value for V3S got BIT18 disabled but need it ?
<jelle>
montjoie: but they also hardcoded python2 in the binman shebang so it might just work without it..
<montjoie>
will try:)
<jelle>
montjoie: but PYTHON=python2 should just work
<montjoie>
my "toolcain" patch Makefile compile and revert just after
<jelle>
montjoie: yup
<montjoie>
pfff uboot need python2.7
<montjoie>
techping: slot 0 is "anyphy" so if it not work on slot 1, perhaps slot>1
<MoeIcenowy>
montjoie: I think we can just force the CLK_SEL to be 1 (24MHz)
<montjoie>
missing _libfdt.so
<montjoie>
I was trying to test your patch but unable to build recent uboot
<montjoie>
I will check it
<MoeIcenowy>
montjoie: have you read my words about syscon reg bit 18?
<montjoie>
(or a bug)
<montjoie>
oh uboot doesnt support KBUILD_OUTPUT:(
2017-06-04
<MoeIcenowy>
montjoie: it seems that it's needed to have a dt property to control the syscon register's bit 18 (CLK_SEL)
<montjoie>
hacked so many part of stmmac...
<montjoie>
MoeIcenowy: didnt see better than that
<montjoie>
MoeIcenowy: yes hidden:)
<montjoie>
could you paste your modifications ?
<MoeIcenowy>
montjoie: so strange... if I use newly added allwinner,sun8i-v3s-emac compatible, enabling eth0 will fail with "dwmac-sun8i 1c30000.ethernet eth0: Could not attach to PHY"
<montjoie>
perhaps just a "bool external_phy" will do the trick
<MoeIcenowy>
montjoie: sufficient.
<montjoie>
MoeIcenowy: why current emac is not sufficient for v3s ?
<MoeIcenowy>
montjoie: maybe I should now make V3s driver -- V3s is like the H3, but without external *MII interface, only ephy
<MoeIcenowy>
montjoie: fix sent.
<MoeIcenowy>
montjoie: oh I think just run assert on the reset line is OK even if it's already asserted
<MoeIcenowy>
montjoie: the problem starts to become complicated
<MoeIcenowy>
montjoie: please remove the if sentence in my patch when testing
<MoeIcenowy>
montjoie: I added a ` reset_control_assert(gmac->rst_ephy); ` before ` ret = reset_control_deassert(gmac->rst_ephy); `
<MoeIcenowy>
paultag: the someone is montjoie, who talked to you just before
<montjoie>
paultag: emac is in linux-next
<montjoie>
clearly lack of test from myself on "boot unplugged"
<MoeIcenowy>
montjoie: with cable inserted at boot emac starts properly
<montjoie>
MoeIcenowy will try
<MoeIcenowy>
montjoie: current linux-next got "EMAC reset timeout" and "probe of 1c30000.ethernet failed with error -12" with no cable plugged at boot with Orange Pi PC
2017-06-03
<montjoie>
not so serious, it just delay a bit my personnal "kernelci"
<willmore>
montjoie, I have lots of relays, but you're probably not on my continent. :(
<montjoie>
it was so few used also:(
<montjoie>
pfff first time I power for long time my allwinner cluster, power relay die
2017-06-02
<montjoie>
mripard: and syscon@ have a leading 0, so I will probably need to resend
<montjoie>
because I forget to add the cover letter (wens> montjoie: you can send all 3, but explain in your cover letter that the 3rd is only for reference)
<mripard>
montjoie: I'm confused, why do you send patches you don't want to be merged?
<montjoie>
ok found it on schematics
<montjoie>
for bpim2+ its PD6 but cannot find where to check why its it
<montjoie>
same in schematics ?
<montjoie>
and how to know if a regulator is necessary ?
<montjoie>
I try to update properly my DT for bpim2+/opi+/opipc2 but how to know which pins is for "gpio_out" ? in schematics?
<wens>
montjoie: because I have to reorder the patches and pull out a lot of stuff :/
<montjoie>
why not send the bpim3 since it apply cleanly ?
<wens>
montjoie: yup
<montjoie>
wens: which of your branch should I use for a83t ? a83t-ccu-mmc-usb ?
<wens>
montjoie: you can send all 3, but explain in your cover letter that the 3rd is only for reference
<montjoie>
or I could just send 2 of 3 patchs (syscon + a83t only)
<montjoie>
wens: could you send your patch for bpim3 ? it will permit that I send all dwmac-suun8i patchs for a83t
<montjoie>
since the commit only speaked about sun8i-dwmac i thinked it was an error
<montjoie>
it seems I see bad
<montjoie>
and it seems that the column modifed was A20
<montjoie>
dont know, just fixed en unrelated change
<rellla>
montjoie: does A10s have GMAC?
<mripard>
montjoie: well, I guess he'll be the one fixing up the merge conflicts then.
<montjoie>
mripard: too late for DT, I see them in linux-next so certainly via net-next
2017-06-01
<willmore>
montjoie, for reals? Yay! Congratulations!
<montjoie>
possible, need to check net-next rules
<montjoie>
started on 26/11/2015...
<montjoie>
YEAH! dwmac-sun8i applied
2017-05-31
<montjoie>
:)
<montjoie>
lots of user reports the famous "reset EMAC timeout"... anyone here with it ?
<montjoie>
and see if an EMAC reset timeout occur please
<montjoie>
boot with no wire plugged
<montjoie>
Anyone with an opi zero ? (need a net test)
<qschulz>
montjoie: just sent the fix for the bug you reported. I've slighlty changed the patch but that shouldn't impact the test you did. Feel free to retest it and add your Tested-by :)
2017-05-14
<montjoie>
for my ethernet serie
<montjoie>
mripard: could you accept all 4 syscon patchs for letting the next shot smaller ?
2017-05-13
<montjoie>
qschulz: why not adding a delay for only the first one ?
<qschulz>
montjoie: thanks for reporting the bug and testing the patch. I get also this ETIMEDOUT (-110) once when inserting the module, basically the first interrupt isn't received in the first second of delay I let him
2017-05-12
<montjoie>
still get "thermal thermal_zone0: failed to read out thermal zone (-110)"
<montjoie>
qschulz: your patch seems working (at least no crash since 30 min of "watch sensors")
<montjoie>
so lost!
<montjoie>
ouch an user answering to my first sun8i-emac driver serie...
<montjoie>
need to finish the powercontrol by arduino
<qschulz>
montjoie: okay, no worries
<montjoie>
sorry, could reboot it only at lunch (in 3 hours)
<montjoie>
qschulz: started the board just before going to work, forget that it crash few time after..
<qschulz>
montjoie: did you have time to test it?
<swiftgeek>
montjoie: i'm clueless ;D
<montjoie>
swiftgeek: why dwmac will not fit in 4.12. I am near sure it will
2017-05-11
<qschulz>
montjoie: ok, no reason it wouldn't work but better be sure. I'll send the patch tomorrow if you can confirm it works on your board
<montjoie>
qschulz: I will test it in 4 hour, the board is off/remote