karolherbst has quit [Read error: Connection reset by peer]
karolherbst has joined #panfrost
warpme has joined #panfrost
lcagustini has quit [Remote host closed the connection]
lcagustini has joined #panfrost
rasterman has joined #panfrost
<kusma>
mntirc: I'm really confused why this doesn't work on a311d for you. It works fine on my VIM3, which has the same display controller. Are you using some special setup of display planes etc?
<kusma>
It could be that the display controller reports supporting this for all planes, but in reality only supporting it on some or something like that.
<kusma>
I'm just running "plain" Weston on Debian on that board, BTW.
lcagustini has quit [Remote host closed the connection]
lcagustini has joined #panfrost
chewitt has joined #panfrost
lcagustini has quit [Remote host closed the connection]
lcagustini has joined #panfrost
<bbrezillon>
stepri01: if you push things to drm-misc-next, can you also take alarumbe's series?
sally has quit [Quit: sally]
sally has joined #panfrost
<mntirc>
kusma: here's how it looks like for 1 user, like the display is cutting out randomly. https://i.imgur.com/iSB84Ez.mp4 it happens on both sway and gnome on two different machine types (pocket and classic reform), the common denominator is both use DSI output.
<kusma>
Heh, OK. DSI is a quite big difference from what I have here, yeah.
<daniels>
yeah, rockchip has their own display controller that has nothing to do with aml's
<kusma>
It would be interesting to see if it happens with HDMI output.
<mntirc>
kusma: good point, we can try that
<kusma>
mntirc: Yeah, so this is almost certainly a problem with the meson display driver in the kernel, just triggered by Mesa by us enabling a previously unsupported mode.
<mntirc>
kusma: ah, so this AFBC patch affects scanout? i need to catch up on the effects of it
<kusma>
You really want to use 32x8 for scanout if you can, because that has better caching behavior, which should lead to both better performance and power consumption.
<kusma>
mntirc: Well, Panfrost started advertising support for more DRM modifiers...
<mntirc>
narmstrong: any ideas about this maybe ^ ?
<kusma>
That means the display driver and Mesa will negotiate a diffrerent preferred mode.
<mntirc>
narmstrong: mesa AFBC negatively impacting DSI scanout on a311d?
<mntirc>
kusma: understood, thanks
<kusma>
But in this case, it seems the display might have some issues handling the output.
<mntirc>
kusma: hmm, it's independent on display model (and in classic this goes via TI dsi->eDP bridge)
<mntirc>
so maybe something internal in a311d?
<kusma>
Sorry, I meant the display-out
<mntirc>
gotcha
<kusma>
I honestly don't know enough about DSI etc to know if AFBC could even be carried over the wire all the way to the display there.
<daniels>
looking at drivers/gpu/drm/meson/meson_venc.c, I wonder if the timings need to be adjusted to push more FIFO at 32x8 tiling?
<daniels>
no AFBC isn't carried over the wire
<mntirc>
ok, we can look into that and will keep the mesa revert patch in the meantime
<kusma>
Yeah, keeping that revert that isn't going to make things worse than they were in 24.3 for you. But once it can reliably work for you, you probably want to switch on 32x8 support again.
<narmstrong>
mntirc: so, the way afbc has been integrated into A311D, means yes it can miss a vsync on load
<narmstrong>
but, otherwise it's the same
<narmstrong>
AFBC has been integrated and validated with the ARM mali blob, so I'm pretty sure it works fine :-)
<mntirc>
narmstrong: aha, thanks for confirming! so we need to tweak something about vsync or do you have any other hunches?
<kusma>
Miss a vsync isn't the same as blacking out the display entirely for a frame, though?
soreau_ has joined #panfrost
soreau_ has quit [Remote host closed the connection]
soreau_ has joined #panfrost
soreau has quit [Ping timeout: 480 seconds]
patteone has joined #panfrost
patteone has quit []
josch has joined #panfrost
<josch>
hi, i have been reading the discussion re a311d flickers in the logs and just came by to say that i do see occasional (about twice per minute) flickers with hdmi
<josch>
no idea if this supports the current hypothesis of the cause of the error or if it's a totally different thing
<josch>
but reverting the AFBC commit also seems to have fixed it
<narmstrong>
It should not black out, neither flicker, it should at worse duplicate a frame, if you encounter flickering it means you're either hitting a bandwidth issue or some HDMI signal issues, it may be caused by AFBC because it does much more DDR access
<narmstrong>
I remember having issues with RGB565 + SPLIT + WIDEBLK
<daniels>
it shouldn't be in 16bpp tho
chewitt has quit [Quit: Zzz..]
soxrok2212 has quit [Read error: Connection reset by peer]
soxrok2212 has joined #panfrost
chewitt has joined #panfrost
chewitt has quit [Read error: Connection reset by peer]
soxrok2212 has quit [Read error: Connection reset by peer]
soxrok2212 has joined #panfrost
<josch>
mntirc, narmstrong: with pocket reform it's dsi but i observe the flicker effect as well on hdmi with a311d and reform motherboard. The flicker goes away after reverting the AFBC commit. I took a bad video of the flicker effect on my tv here: https://mister-muffin.de/reform/a311d-hdmi-flicker.mov
<josch>
i noticed that when i increase the video size, then it flickers more often
<josch>
the whole screen goes black for a fraction of a second
<josch>
which is the same effect that can be seen in deianara's video (just more frequent there)