<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Piotr:<br>
</p>
<div class="moz-cite-prefix">On 3/31/22 22:53, Piotr Oniszczuk
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:B7CD9D55-9F2D-42F4-9D04-17C6A5FEBB08@gmail.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Wiadomość napisana przez Andy Yan <a class="moz-txt-link-rfc2396E" href="mailto:andy.yan@rock-chips.com"><andy.yan@rock-chips.com></a> w dniu 31.03.2022, o godz. 14:13:
Piotr:
What soc is on you board? rk3566 or rk3568?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
it is rk3566 in x96-x6 tvbox</pre>
</blockquote>
<p><br>
</p>
<p>RK3566? Maybe that is the problem.</p>
<p><br>
</p>
<div class="de1">plane[43]: Esmart1-win0
</div>
<div class="de1"> crtc=(null)
</div>
<div class="de1"> fb=0
</div>
<div class="de1"> crtc-pos=0x0+0+0
</div>
<div class="de1"> src-pos=0.000000x0.000000+0.000000+0.000000
</div>
<div class="de1"> rotation=1
</div>
<div class="de1"> normalized-zpos=1
</div>
<div class="de1"> color-encoding=ITU-R BT.601 YCbCr
</div>
color-range=YCbCr limited range
<p>From your dri/state dump, Plane 43 is Esmart1.</p>
<p>Cluster1, Esmart1, Smart1 are special on rk3566, they are</p>
<p>mirror window of Cluster0, Esmart0, Esmart0. That means</p>
<p>the software can't program a independent framebuffer for</p>
<p>these three windows. They can only share the fb address set</p>
<p>in Cluster0, Esmart0, Smart0.</p>
<p>For rk3566, we only use it for two VP display same content:</p>
<p>assign Cluster0,Esmart0,Smart0 to VP1 for primary display(MIPI),</p>
<p>assign Cluster1,Esmart1, Smart1 to VP0 for extend display(HDMI)</p>
<p>we handle this logic in Android hwc:</p>
<p>When a hdmi is connected, hwc will commit Esmart1 with Esmart0
with the <br>
</p>
<p>same fb and src buffer size, the dst can be different(by window
scale)</p>
<p><br>
</p>
<p>I have code comment in my downstream kernel and explained this
detail when Sascha start submit this serials.<br>
</p>
<blockquote type="cite"
cite="mid:B7CD9D55-9F2D-42F4-9D04-17C6A5FEBB08@gmail.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
I have a scripts[0] use io[1] command to dump the VOP2 register you can use it dump the register configuration when you meet a display failure,
then send the dump to me, maybe I can figure out something.
[0]<a class="moz-txt-link-freetext" href="https://github.com/andyshrk/buildroot/blob/2022/board/andyshrk/rootfs_overlay/usr/bin/vop2_dump.sh">https://github.com/andyshrk/buildroot/blob/2022/board/andyshrk/rootfs_overlay/usr/bin/vop2_dump.sh</a>
[1] <a class="moz-txt-link-freetext" href="https://github.com/andyshrk/io">https://github.com/andyshrk/io</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Andy
Pls see <a class="moz-txt-link-freetext" href="https://pastebin.com/CHmu9s22">https://pastebin.com/CHmu9s22</a></pre>
</blockquote>
<p><br>
</p>
<p>The dump is a little strange, I will check it in the later night.<br>
</p>
<blockquote type="cite"
cite="mid:B7CD9D55-9F2D-42F4-9D04-17C6A5FEBB08@gmail.com">
<pre class="moz-quote-pre" wrap="">
I put dumps for following scenarios:
1.
-boot
-modetest -s 69@67:1920x1080 -> ok
-modetest -P 43@67:1920x1080@NV12 -> green screen
2.
-boot
-modetest -s 69@67:1920x1080 -> ok
-modetest -P 49@67:1920x1080@NV12 -> ok (but shifted horizontally by about 5% of screen width)
(setting palne#49 fixes plane #43. Here i set plane #49 but not yet setting #43)
3.
-boot
-modetest -s 69@67:1920x1080 -> ok
-modetest -P 49@67:1920x1080@NV12 -> ok (but shifted horizontally by about 5% of screen width)
-modetest -P 43@67:1920x1080@NV12 -> now ok (but shifted horizontally by about 5% of screen width)
</pre>
</blockquote>
</body>
</html>