ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
vicencb has quit [Quit: Leaving.]
_whitelogger has joined #linux-rockchip
vstehle has quit [Ping timeout: 244 seconds]
<levd> mrjay: that doesn't work. still the same.
yann has quit [Ping timeout: 272 seconds]
<levd> this is log with some DEBUG turn on: https://0x0.st/zpnX.txt
<levd> Hi all, I get passed that by adding "regulator-min-microvolt = <430000>;" in vdd_log , which make the kernel happy.
<levd> This is related to the U-Boot commit 7ba3182e2d92190b7512db35ecda71970a206207. But I wonder why the rk3399-firefly.dts in mainline kernel still has "regulator-min-microvolt = <800000>;".
<levd> I failed to understand this statement for the commit above: "the min output value is not 800000mV for the PWM2 io domain has changed to VCC3V0 instead of VCC1V8 in rockchip evb, we need to correct it with the value measured when PWM2 output HIGH.".
<levd> Anyone mind to explain it a bit?
_whitelogger has joined #linux-rockchip
vstehle has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
<tomeu> wens: nice!
<tomeu> btw, we would like to get a basic desktop experience working stably for mesa 19.2 on rk3288 and rk3399
<tomeu> including browsers
<tomeu> so if you find any problems when testing with mesa master, please jump into #panrfost and report
<EmilKarlson> sounds ambitious
matthias_bgg has joined #linux-rockchip
<wens> tomeu: looks like the issue from yesterday was an unhandled/unimplemented ALU op
wadim_ has joined #linux-rockchip
<EmilKarlson> tomeu: could you confirm that I only need to build mesa on top of debian buster?
<EmilKarlson> eballetbo: do you actually have some build scripts already?
<wens> only mesa needs to be built
<EmilKarlson> eballetbo: for the deb
<tomeu> EmilKarlson: I think buster should have all dependencies, yes
<tomeu> and I guess you already run your own kernel
<EmilKarlson> yes, I follow mainline now
<EmilKarlson> wens: btw. now I got the thing working, user error
<wens> EmilKarlson: cool
<EmilKarlson> [169201.771] (II) modeset(0): glamor X acceleration enabled on panfrost
<EmilKarlson> tomeu: I get a lot of
<EmilKarlson> [169634.892606] panfrost ff9a0000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x9236c00, tail=0x9236c00
<EmilKarlson> [169634.892621] panfrost ff9a0000.gpu: gpu sched timeout, js=0, status=0x58, head=0x9236c00, tail=0x9236c00, sched_job=000000000f238f13
<EmilKarlson> seems to be spamming at 2000Hz that message
<EmilKarlson> tomeu: this is linux-5.2.2, is this something that was fixed
<tomeu> don't think it's related to the kernel
<tomeu> if you are able to run xwayland with PAN_MESA_DEBUG=trace then you should be able to see the cmdstream and find the job at 0x9236c00
<EmilKarlson> tomeu: this is Xorg with glamor
<tomeu> well, I'm assuming that you are running Xwayland
<tomeu> ah, ok
<tomeu> then run X with that env var
<tomeu> and look for a job header at the address pointed to by head in one of those faults
<EmilKarlson> wens: do you see this one?
<tomeu> but all this is more appropriate for #panfrost :)
rellla has quit [Quit: see you later]
<EmilKarlson> where does that trace go to?
<wens> EmilKarlson: don't remember seeing anything from the kernel
ldevulder has joined #linux-rockchip
maz has quit [Ping timeout: 244 seconds]
<eballetbo[m]> Emil Karlson: I don't have scripts yet to create the packges, not. If you want to give a try here is the image:
<eballetbo[m]> You need a sdcard or pendrive > 16GB, and then you can boot with Ctrl-U if you're in developer mode
<eballetbo[m]> Remember is only a test image and It is annoying that s2r is broken again :-(
<EmilKarlson> where is s2r broken, I did not notice anything?
<EmilKarlson> I ran also linux-5.3-rc1 for a few days
<eballetbo[m]> oh, so s2r works for you? it fails here
<EmilKarlson> I haven't noticed anything
<EmilKarlson> the only hack I have that mwifiex gets unloaded on suspend
<EmilKarlson> mwifiex broken in so many ways
<eballetbo[m]> interesting, I'll take a deeper look, on my case when I do a s2r then doesn't wakeup, I didn't debug yet what is happening
<EmilKarlson> since which kernel version is this?
<eballetbo[m]> 5.3-rc1
<eballetbo[m]> same as you
<EmilKarlson> well I reverted to 5.2.2, since kms was slow
<EmilKarlson> but I am moderately sure I suspended at some point
<eballetbo[m]> hmm, maybe is usb who is not working after suspend as I'm booting from external USB pendriver
<EmilKarlson> could be yes
<EmilKarlson> I never suspend when powered, and USB is there when powered
<EmilKarlson> so this fails for you 100% of measured attempts?
<eballetbo[m]> yes, fails all the time
<EmilKarlson> my guess is I suspended 2 to 4 times
<EmilKarlson> I can check logs later
rellla has joined #linux-rockchip
<eballetbo[m]> don't worry, is something I need to look at some point but won't be now
<EmilKarlson> several signs point to 5.3 being LTS kernel, so I'll also put heavy effort on it at some point
<EmilKarlson> interactive ui slowdown is really nasty to debug, as you don't get numbers that are not trampled by things that you don't want to measure
<EmilKarlson> for all I know, it could even be just imagination
<EmilKarlson> also right now I am very concerned that I don't even know, what the bottle necks are otherwise
<EmilKarlson> just strace recursively from init and see, which syscalls total the most time
maz has joined #linux-rockchip
cyteen has joined #linux-rockchip
Putti has quit [Remote host closed the connection]
adjtm has quit [Ping timeout: 268 seconds]
Greyztar has joined #linux-rockchip
vicencb has joined #linux-rockchip
Putti has joined #linux-rockchip
field^Zzz1 has joined #linux-rockchip
adjtm has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
maz has quit [Disconnected by services]
chewitt has joined #linux-rockchip
perr has joined #linux-rockchip
maz has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
perr has quit [Remote host closed the connection]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-rockchip
perr has joined #linux-rockchip
perr has quit [Remote host closed the connection]
return0e has quit [Ping timeout: 246 seconds]
chewitt has quit [Ping timeout: 258 seconds]
yann has joined #linux-rockchip
robogoat has joined #linux-rockchip
return0e has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 245 seconds]
adjtm has quit [Ping timeout: 245 seconds]
adjtm has joined #linux-rockchip
afaerber has joined #linux-rockchip
yann has quit [Ping timeout: 244 seconds]
<EmilKarlson> wens: how did you compile your package, which meson flags?
<wens> yeah, and cross compile
nsaenz has quit [Ping timeout: 245 seconds]
nsaenz has joined #linux-rockchip
yann has joined #linux-rockchip
<yann> Anyone here played with HDMI-CEC ? On a rk3399 with CONFIG_DRM_DW_HDMI_CEC and CONFIG_MEDIA_CEC_SUPPORT I do get the /dev/cec0 device, but there doesn't seem to be any kind of dialog with the TV, it just does not appear in the cec topology...
vicencb has joined #linux-rockchip
scelestic has quit [Remote host closed the connection]
<EmilKarlson> wens: thanks, seems to work
<EmilKarlson> next part, I guess, would be the debian packages
scelestic has joined #linux-rockchip
nolan_ has joined #linux-rockchip
nolan_ has left #linux-rockchip ["Closing Window"]
<inode> anyone else encountered an error to the effect of "Unable to handle kernel paging request at virtual address <addr>" with the PC lurking somewhere in cfb_imageblit() (called from drm_fb_helper_cfb_imageblit()) since v5.3-rc1?
stikonas has joined #linux-rockchip
<EmilKarlson> did not see it
ldevulder_ has quit [Quit: Leaving]
stikonas has quit [Remote host closed the connection]
field^Zzz1 has quit [Ping timeout: 245 seconds]
vicencb has quit [Quit: Leaving.]