Guest5448 has quit [Remote host closed the connection]
sputnik has joined #linux-amlogic
sputnik is now known as Guest9471
Guest9471 has quit [Client Quit]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Client Quit]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik has joined #linux-amlogic
sputnik is now known as Guest6190
vagrantc has quit [Quit: leaving]
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-amlogic
pulpoff has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
tdebrouw has joined #linux-amlogic
JerryXia1 is now known as JerryXiao
chewitt has quit [Quit: Zzz..]
warpme__ has joined #linux-amlogic
camus has quit [Ping timeout: 256 seconds]
camus has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
camus1 has joined #linux-amlogic
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
Guest6190 has quit [Remote host closed the connection]
Guest6190 has joined #linux-amlogic
Guest6190 has quit [Remote host closed the connection]
Darkmatt- has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #linux-amlogic
<
tdebrouw>
narmstrong: I'm using a A311D, with a dsi86 attached to the mipi output.
<
tdebrouw>
I see an image
<
tdebrouw>
but every 30 - 60 seconds
<
tdebrouw>
I see a 'shake' in the output
<
tdebrouw>
like a judder
<
tdebrouw>
it seems like I missed some sync
<
tdebrouw>
when running stress-ng, I can increase it a lot
<
tdebrouw>
stress-ng --vm 8 --vm-bytes 512M --fork 4 --timeout 1000s
<
tdebrouw>
this will give me constant misses
<
tdebrouw>
I can generate a test image in the dsi86, and this never shakes
<
tdebrouw>
Also, the dsi has error registers, but it never mentions some sort of sync loss
<
tdebrouw>
the mipi outputs 1920 * 1080 @ 60
<
tdebrouw>
burst mode on/off has no influence
<
tdebrouw>
increasing the hs_rate (mipi clock) manually has no influence
vagrantc has joined #linux-amlogic
<
tdebrouw>
changing the video timings (cvt -> cvt rb)
<
tdebrouw>
has no influence neither
<
tdebrouw>
any idea what I could try next?
<
tdebrouw>
can you try it on your setup?
<
tdebrouw>
narmstrong: thanks.
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 264 seconds]
camus1 is now known as camus
<
narmstrong>
tdebrouw: hi, nice you made this work, I was wondering it it would work
<
narmstrong>
tdebrouw: I'm not a dsi expert, but maybe the mipi clock is too low and would need some margin
<
narmstrong>
tdebrouw: stressing the system will cause delays on the DDR reads, thus adding some delays to the video paquets
<
narmstrong>
other dsi glues adds some margin, but so far it worked without it
<
narmstrong>
note I also see shaking on the VIM3 DSI display
<
narmstrong>
but I never saw such shaking on the A113D, which is a much simpler design
<
narmstrong>
but since our mipi clock base and vclk base comes from the same source, it would need some logic
<
narmstrong>
the A311D supports different clocks, but same it would need to be supported
pulpoff has quit [Quit: Client closed]
<
tdebrouw>
narmstrong: I added some functionality to specify the maximum allowable mipi clock (hs_rate) to the panel definition
<
tdebrouw>
and it's currently specified as 4 * pixelclock.
<
tdebrouw>
( +- 1131 MHz) - so a DSI clock around 565MHz
<
tdebrouw>
which gives me an image
<
tdebrouw>
Could it be some internal axi bus misconfiguration?
jernej has joined #linux-amlogic
<
tdebrouw>
I guess I should take a good look to the amlogic tree?
<
narmstrong>
tdebrouw: could you reduce the VIU_OSD_HOLD_FIFO_LINES() in drivers/gpu/drm/meson/meson_viu.c ?
<
narmstrong>
31 is very high, and mainly use for HDMI, but on A113D, 31 is too high and 24 fixed some display issues
nashpa has joined #linux-amlogic
rapha has quit [Ping timeout: 256 seconds]
dliviu has quit [Ping timeout: 256 seconds]
kilobyte_ch has quit [Ping timeout: 256 seconds]
rapha has joined #linux-amlogic
kilobyte_ch has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
<
tdebrouw>
narmstrong: that fixes the issue on my side. Thanks!
camus1 has joined #linux-amlogic
camus has quit [Remote host closed the connection]
camus1 is now known as camus
chewitt has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
sputnik has joined #linux-amlogic
sputnik is now known as Guest4917
rockosov has quit [Quit: Connection closed for inactivity]
warpme__ has quit [Quit: Connection closed for inactivity]
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
tdebrouw has quit [Quit: Leaving.]
jernej has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #linux-amlogic
buzzmarshall has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 252 seconds]
Darkmatter66 has joined #linux-amlogic
Darkmatter66 has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #linux-amlogic