<amstan>
bashintosh: i'm pretty sure they get autodetected
<bashintosh>
oh right
<bashintosh>
amstan: do you use HPD as well as AUX for eDP? I am using the Firefly RK3288 to interface to an eDP->MIPI board/LCD but the Firefly has no HPD out, only AUX. I think HPD is a requirement (from VESA documentation). So far the link training fails, even if I set all the proper timings
<amstan>
we actually have hpd broken on a few systems, so we just hardcode it to always be there
<amstan>
so that's duable
<amstan>
doable*
<bashintosh>
with hardcode it you mean patching the eDP initialization in the transmitter driver or a hardware modification?
<amstan>
someone forgot to connect the hpd pin, so we used a pullup on the pin to force it on(as if there's a display there)
<amstan>
which there was
<amstan>
and that worked
<amstan>
though i'm not the best person to ask all this, i barely had it working
<bashintosh>
mmh but you had an HPD pin on the source right? That's what is really confusing on the Firefly pinout... No HPD, not even in their schematics. Thx anyway amstan !
<amstan>
what do you mean by the source?
<bashintosh>
the eDP source
<amstan>
isn't that the rk3288?
<bashintosh>
yes, I cannot find HPD - there is one onto the HDMI pinouts but I don't think it's related to eDP
<amstan>
or are you just excited that you found the existance of edp_hpd?
<amstan>
lol
<bashintosh>
Both :) I have to see how to apply that to the Firefly configuration BUT at least I am not looking around in vain anymore
<bashintosh>
amstan: the rk32-dp driver has this function which is executed after rk32_edp_init_edp() returns 0, so maybe in my case the link training is failing for some other reason: https://paste.fedoraproject.org/251252/
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 272 seconds]
<amstan>
rperier: have you tried the mali stuff in arch btw? it works wonderfully for me
<mmind00>
amstan: great to hear :-)
<amstan>
mmind00: at the same time this other guy is reporting flickering on speedy, so i was trying to probe around and see what rperier's experience is like
<mmind00>
amstan: I sometimes also see flickering (I guess mainly in webgl parts) ... which seems to have increased with the most recent version (r5-something)
<mmind00>
amstan: waiting just now for the r6 stuff to land (kernel part is already in the tracker)
<mmind00>
amstan: I think the r22 is the chromeos version of the binary libraries
<amstan>
woah! ok.. this flickers
<amstan>
this is not good
<mmind00>
amstan: I guess possible flickering source is the gpu/cpu fencing ChromeOS has, that is not in mainline
<amstan>
yeah, so i just upgraded my arch 3.14 kernel and it flickers now :(
<rperier>
amstan: not yet, I will retry I think, if it works fine for you
<rperier>
:)
<amstan>
kde composition saves me from most of it, but it flickers when my cursor's y is under 20 or so in sddm
<rperier>
(I mostly did mainline and yocto tasks on my veyron for now)
<naobsd>
how about vpu(encoder/decoder) on ChromeOS?
<amstan>
naobsd: we use both of the afaik
<naobsd>
I'm curious about hangouts quality on ChromeOS :)
<naobsd>
amstan: sounds nice :)
<amstan>
hangouts video quality is pretty good
<amstan>
if only hangouts was better in general though
<rperier>
btw, do you need userspace tool to get edp working with the chromeos kernel ? (some mali stuffs for example) it works like a charm on arch, however when I rebuild the chromeos kernel myself from yocto and when I try to boot a minimal image, the kernel hangs when edp starts...
<rperier>
(that's the same kernel , same config... same dtb... the toolchain is just different but other kernels work just fine)
<amstan>
you shouldn't need userspace, edp starts working early in the boot process, you should see messages scroll by
<amstan>
sounds like you're missing some config options
<amstan>
dabea37 FROMLIST: drm/rockchip: default enable win2/3 area0 bit
<amstan>
one of those causes armsoc flickering i think ^
<amstan>
will debug later today
<mmind00>
amstan: woohoo \o/ ... I don't think there was a prize, but dbehr was simply very sceptic if a significant number of people would want to use the chromeos mali drivers
<amstan>
i convinced him to get us a new binary
<mmind00>
but it is so cool to see the whole adoption of rockchip chromebooks :-D
<amstan>
still waiting for the greg alexander guy to show up too
<amstan>
greggypoo: oh! hi
<amstan>
mmind00: now dbehr's watching your repo too!
<mmind00>
:-D
premoboss has joined #linux-rockchip
gb_master has quit [Remote host closed the connection]