gaston1980 has quit [Remote host closed the connection]
gaston1980 has joined #linux-sunxi
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 272 seconds]
camus1 is now known as kaspter
robogoat has joined #linux-sunxi
TheSeven has quit [Ping timeout: 244 seconds]
[7] has joined #linux-sunxi
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 258 seconds]
gaston1980 has quit [Quit: Konversation terminated!]
daregap has joined #linux-sunxi
cmeerw has joined #linux-sunxi
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 272 seconds]
camus1 is now known as kaspter
camus1 has joined #linux-sunxi
kaspter has quit [Read error: Connection reset by peer]
camus1 is now known as kaspter
ec0_ is now known as ec0
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
afaerber has quit [Ping timeout: 240 seconds]
afaerber has joined #linux-sunxi
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 256 seconds]
camus1 is now known as kaspter
yann|work has joined #linux-sunxi
dev1990 has joined #linux-sunxi
kaspter has quit [Ping timeout: 258 seconds]
camus1 has joined #linux-sunxi
camus1 is now known as kaspter
<gediz539>
hi all. what is a good alternative for lima-memtester on mainline kernel?
_rze has quit [Ping timeout: 260 seconds]
rzerres has joined #linux-sunxi
<mripard>
gediz539: it doesn't really exist unfortunately
matthias_bgg has joined #linux-sunxi
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 256 seconds]
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 246 seconds]
camus1 is now known as kaspter
florian_kc has joined #linux-sunxi
<gediz539>
mripard: would it be cool if kmscube is integrated with memtester?
<KotCzarny>
and with data corruption checker most importantly
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-sunxi
<gediz539>
KotCzarny: to see which byte/data lane is problematic like in memtester or another concept?
<mripard>
yeah, that's the most important part
<KotCzarny>
i think lima-memtester includes libjpeg-turbo to stress cpu and also to check the data output
<gediz539>
i see. i will do my best. i have little to no idea on graphics stack but apparently this is a common need.
<KotCzarny>
lima-memtester stresses many of the components, cpu, gpu, memory
<gediz539>
mripard: this is off-topic but, I've updated the patch and forgot to cc maintainers while sending it. did not want to double-post too. in case you did not see, there's a uart4 patch for A64: https://lists.denx.de/pipermail/u-boot/2020-July/418514.html
<gediz539>
KotCzarny: i'll try to understand how it works.
<mripard>
gediz539: you should resend it then
florian_kc is now known as florian
<gediz539>
mripard: okay, thanks. i just did not want to create too much noise.
<clementp[m]>
megi: hdmi_audio is now disabled by default
<clementp[m]>
for panfrost dvfs i think I made an issue when I rebased it :(
<megi>
clementp[m]: I noticed and enabled it specifically on Opi 3
<megi>
thanks :)
<clementp[m]>
megi: Did you make it work ?
<megi>
no
<megi>
I noticed that lima seems to have a different order of initialization which works
<megi>
so maybe just swapping the order of those call will make it work
<megi>
I'm in the middle of some other driver work, so I didn't try
<clementp[m]>
Yes for pandrost
<clementp[m]>
I agree that there is an issue in the OPP init :(
<clementp[m]>
but for hdmi_audio w/o panfrost did you try it ?
<megi>
not yet the current version, but previous one worked
<clementp[m]>
Werner: even with this series applied GPU DVFS doesn't work properly on Allwinner H6, in the v2 series I made a mistake and I will send a v3
kaspter has quit [Ping timeout: 246 seconds]
<Werner>
clementp[m]: okay, thanks.
kaspter has joined #linux-sunxi
<clementp[m]>
You can retest it maybe it has been fixed, I don't know if it's frequency/voltage that are unstable or if it's another problem maybe CPU/GPU sync when both have DVFS enabled but I don't know...
suprothunderbolt has quit [Ping timeout: 246 seconds]
cnxsoft1 has quit [Read error: Connection reset by peer]
cnxsoft has joined #linux-sunxi
dddddd has joined #linux-sunxi
camus1 has joined #linux-sunxi
kaspter has quit [Ping timeout: 246 seconds]
camus1 is now known as kaspter
jbrown has joined #linux-sunxi
tnovotny has joined #linux-sunxi
_0x5eb_ has quit [Remote host closed the connection]
matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
suprothunderbolt has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
matthias_bgg has quit [Ping timeout: 272 seconds]
lerc has quit [Ping timeout: 240 seconds]
lerc has joined #linux-sunxi
[LAWNMOWERMAN] has quit [Quit: The machine is gonna show you who you are.]
<martinayotte>
I discovered that on Micro-A20 and "dmesg" was flooded by errors with PMIC, and when I discovered that also other I2C were also broken, I've looked at i2c-mv64xx.c history.
<martinayotte>
I don't know why it seems that only A20 is affected and the issue not seen on A64/H3/H5 ...
cmeerw has quit [Ping timeout: 272 seconds]
<mripard>
martinayotte: the A64 doesn't use the i2c bus to communicate with the PMIC, and the H3 and H5 usually don't have a PMIC
<mru>
almost all systems use i2c for something
<megi>
martinayotte: I know, that's why I reverted it in my 5.8 branch
<megi>
A13 is also broken by it
<megi>
not sure why
jstein has quit [Quit: quit]
<mripard>
mru: right, but it might be much easier to notice if the system simply doesn't boot
<mripard>
megi: on all the SoCs prior to the A31 (so A10-A20), if you shut down the bus clock the device is reset
<megi>
ah, that looks like it might be a culprit here
<mripard>
If I had to make a guess, I would bet on that :)
<mru>
A20 boots just fine even if the pmic driver is disabled
<mru>
assuming a reasonable state after u-boot
<mripard>
it's a slightly different case though
<mripard>
if the PMIC driver was disabled you wouldn't use the PMIC at all obviously, if it's there but the i2c controller doesn't work, it will try to communicate but timeout
matthias_bgg has joined #linux-sunxi
<mru>
wouldn't it still boot after failing to talk to the pmic?
<megi>
except for stuff that needs regulator_enable to not time out
matthias_bgg has quit [Quit: Leaving]
lkcl__ is now known as lkcl
<martinayotte>
mripard: I'm not talking about PMIC specifically, but all I2C were not working on A20 while working on other SoC.
<martinayotte>
megi: Good ! I didn't check your revert under 5.8.y, I've just look history on 5.7.y ... Maybe you can revert it there too ? Did you got change to chat with Samuel ?
<megi>
yes
qschulz has quit [Read error: Connection reset by peer]