wwilly_ has quit [Ping timeout: 256 seconds]
mszyprow|home has joined #linux-exynos
genii has quit [Quit: Bedtime. See you soon.]
wwilly_ has joined #linux-exynos
Wizzup has quit [Ping timeout: 244 seconds]
Wizzup has joined #linux-exynos
nashpa has quit [Ping timeout: 264 seconds]
nashpa has joined #linux-exynos
wwilly_ is now known as wwilly
wwilly has quit [Quit: Leaving]
wwilly has joined #linux-exynos
dlan has joined #linux-exynos
<mszyprow|home> wwilly: ping
<mszyprow|home> wwilly: i think I've found somthing related to the usb/lan issues on XU3. Could you check if removing all regulator-coupled-* properties from the exynos5422-odroid-core.dtsi fixes it?
genii has joined #linux-exynos
<wwilly> mszyprow|home: hi
<wwilly> will check
<wwilly> I rafine the revert patch
<wwilly> I forgot to send
<wwilly> I check what I did
<wwilly> mszyprow|home: what's the problem you found? inpacting something else?
<wwilly> mszyprow|home: you mean regulator-coupled-* under buck2_reg: BUCK2 and buck3_reg: BUCK3 ?
<mszyprow|home> wwilly: yes
<mszyprow|home> wwilly: i managed to reproduce some usb issues on xu3 with usb pendrive
<mszyprow|home> wwilly: i wonder if this is the same you got
<mszyprow|home> wwilly: disabling regulator coupling seems to fix my issues
<mszyprow|home> wwilly: no idea why yet
<wwilly> ok
<wwilly> with which version you have issue?
wwilly_ has joined #linux-exynos
wwilly_ has quit [Client Quit]
wwilly_ has joined #linux-exynos
wwilly has quit [Ping timeout: 256 seconds]
wwilly_ is now known as wwilly
wwilly_ has joined #linux-exynos
<wwilly_> ping??
wwilly has quit [Ping timeout: 265 seconds]
wwilly_ is now known as wwilly
ojn has quit [Ping timeout: 246 seconds]
ojn has joined #linux-exynos
LiquidAcid has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 260 seconds]
mszyprow|home has joined #linux-exynos
<mszyprow|home> wwilly: v5.6
<mszyprow|home> wwilly: but I've just checked and it is same for current linux-next (20200526)
<mszyprow|home> wwilly: alternatively you can change the regulator-min-microvolt to <925000> for buck3_reg (vdd_int)
<mszyprow|home> wwilly: both seems to be fixing my issue
<mszyprow|home> wwilly: I only need to figure out the bug in coupling code which lowers the voltage too much
<wwilly> I will check that tommorow, I was a bit busy right now
<mszyprow|home> wwilly: okay
<wwilly> but what I change just to have it working without full revert was https://pastebin.com/UM6Z3XSa
<mszyprow|home> wwilly: what about the issue with ondemand gouvernor and dmc devfreq?
<wwilly> I don't know why I was needing opp-shared, and keep operating-points-v2 = <&bus_fsys_apb_opp_table>; in bus_fsys
<mszyprow|home> wwilly: you mentioned that it waits for a paper acceptance
<wwilly> arf no, this is about lan crashing
<mszyprow|home> wwilly: i've checked the clocks once again and also copared your clock dump
<wwilly> yes, the paper is accepted, and I currently busy recording the virtual talk because of lockdown
<mszyprow|home> wwilly: any that change only affects devfreq
<mszyprow|home> wwilly: but it might be enough to change it in a way that the regulator balancing is done right
<wwilly> but, I will provide everything by next week, need to be properly ready release for the conference you see
<mszyprow|home> wwilly: but the source is in the regulator balancing code
<mszyprow|home> wwilly: one needs to trigger it somehow
<mszyprow|home> wwilly: your patch hides it
<wwilly> hide the problem you mean, without fixing it? so why it's running buy just hiding it??
<wwilly> ok, let's discuss tomorrow, family stuff, I'm already late :)
<wwilly> c u toms to discuss plenty
<mszyprow|home> wwilly: i will aswer that question once i find the bug :) now i just found what to change to really avoid it
LiquidAcid has quit [Quit: Leaving]
nashpa has quit [Quit: Going away]
nashpa has joined #linux-exynos
mszyprow|home has quit [Ping timeout: 260 seconds]