From: Piotr Oniszczuk <piotr.oniszczuk@gmail.com>
To: Linux-rockchip@lists.infradead.org
Subject: vop2: 3566 vs 3568: green screen on 3566; on 3568 all ok...
Date: Sun, 24 Dec 2023 13:37:11 +0100 [thread overview]
Message-ID: <7408CE66-E110-4DB2-8B73-856E71E16754@gmail.com> (raw)
Hi *
I have well working video decoding + rendering to drm planes on rk3568.
On rk3566 however video playback gives mr green screen.
Looking on 6.6.8 vop2 sources i see e.g. rk3568_vop_win_data[] is common for 3566 and 3568.
I recall however Andy Yan (rockchip) said:
"But take care that the vop on rk3566 has a special limitation: there are three windows(Cluster1/Esmart1/Smart1) that have a mirror lock, that means they can't be programmed framebuffer address independently , they can only share framebuffer address with Cluster0/Esmart0/Smart0”.
I suspect my 3566 green video issue is somehow result of "too" common vop2 code for 3566 & 3568 variants.
Isn't that 3566 should have dedicated variant code to deal with 3566 limitations mentioned by Andy?
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2023-12-24 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 12:37 Piotr Oniszczuk [this message]
2023-12-25 1:40 ` vop2: 3566 vs 3568: green screen on 3566; on 3568 all ok Andy Yan
2023-12-25 12:14 ` Piotr Oniszczuk
2023-12-26 1:41 ` Andy Yan
2023-12-26 11:22 ` Piotr Oniszczuk
2023-12-27 7:25 ` Kever Yang
2023-12-27 7:36 ` Dragan Simic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7408CE66-E110-4DB2-8B73-856E71E16754@gmail.com \
--to=piotr.oniszczuk@gmail.com \
--cc=Linux-rockchip@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox