From: Andy Yan <andy.yan@rock-chips.com>
To: "Heiko Stübner" <heiko@sntech.de>, "Andy Yan" <andyshrk@163.com>
Cc: hjc@rock-chips.com, dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, sebastian.reichel@collabora.com,
kever.yang@rock-chips.com, chris.obbard@collabora.com,
s.hauer@pengutronix.de
Subject: Re: [PATCH 09/11] drm/rockchip: vop2: Add support for rk3588
Date: Wed, 15 Nov 2023 10:02:42 +0800 [thread overview]
Message-ID: <b8605ecb-0244-4ff7-8338-759011dee1b3@rock-chips.com> (raw)
In-Reply-To: <7034316.0VBMTVartN@diego>
Hi Heiko:
On 11/15/23 07:34, Heiko Stübner wrote:
> Hi Andy,
>
> Am Dienstag, 14. November 2023, 12:28:55 CET schrieb Andy Yan:
>> From: Andy Yan <andy.yan@rock-chips.com>
>>
>> VOP2 on rk3588:
>>
>> Four video ports:
>> VP0 Max 4096x2160
>> VP1 Max 4096x2160
>> VP2 Max 4096x2160
>> VP3 Max 2048x1080
>>
>> 4 4K Cluster windows with AFBC/line RGB and AFBC-only YUV support
>> 4 4K Esmart windows with line RGB/YUV support
>>
>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
> not a review yet, but when testing and the display sets a mode,
> I always get a bunch of
>
> rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
>
> messages in the log (initial mode to console, starting glmark2 from console,
> stopping glmark2 to the console).
>
> I'm not sure what is up with that, have you seen these messages as well
> at some point?
Yes, it will raise POST_BUF_EMPTY when set a mode, it needs some fix
like [0]:
I still trying to find a appropriate way to do it with the upstream
code, as it doesn't affect the
real display function(I must admit that the POST_BUF_EMPTY irq is very
annoying), so l let it as
it is in the current version.
By the way, can you see the glmark2 rending on your HDMI monitor now?
[0]https://github.com/Fruit-Pi/kernel/commit/29af993b46f024360e6d02c0d26c9fd3057aa918
>
> Thanks
> Heiko
>
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2023-11-15 2:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:25 [PATCH 00/11] Add VOP2 support on rk3588 Andy Yan
2023-11-14 11:27 ` [PATCH 01/11] drm/rockchip: move output interface related definition to rockchip_drm_drv.h Andy Yan
2023-11-14 11:27 ` [PATCH 02/11] Revert "drm/rockchip: vop2: Use regcache_sync() to fix suspend/resume" Andy Yan
2023-11-14 11:27 ` [PATCH 03/11] drm/rockchip: vop2: set half_block_en bit in all mode Andy Yan
2023-11-14 11:27 ` [PATCH 04/11] drm/rockchip: vop2: clear afbc en and transform bit for cluster window at linear mode Andy Yan
2023-11-14 11:27 ` [PATCH 05/11] drm/rockchip: vop2: Set YUV/RGB overlay mode Andy Yan
2023-11-14 11:28 ` [PATCH 06/11] drm/rockchip: vop2: rename grf to sys_grf Andy Yan
2023-11-14 11:28 ` [PATCH 07/11] dt-bindings: soc: rockchip: add rk3588 vop/vo syscon Andy Yan
2023-11-16 19:26 ` Rob Herring
2023-11-14 11:28 ` [PATCH 08/11] dt-bindings: display: vop2: Add rk3588 support Andy Yan
2023-11-14 13:44 ` Rob Herring
2023-11-14 21:54 ` Heiko Stübner
2023-11-15 2:45 ` Andy Yan
2023-11-14 11:28 ` [PATCH 09/11] drm/rockchip: vop2: Add support for rk3588 Andy Yan
2023-11-14 23:34 ` Heiko Stübner
2023-11-15 2:02 ` Andy Yan [this message]
2023-11-15 8:24 ` Heiko Stübner
2023-11-15 9:08 ` Sascha Hauer
2023-11-16 7:24 ` Andy Yan
2023-11-16 7:50 ` Sascha Hauer
2023-11-16 8:00 ` Andy Yan
2023-11-16 10:39 ` Andy Yan
2023-11-16 13:47 ` Sebastian Reichel
2023-11-17 7:06 ` Andy Yan
2023-11-17 9:39 ` Sascha Hauer
2023-11-16 19:27 ` Rob Herring
2023-11-17 23:46 ` Jonas Karlman
2023-11-18 0:31 ` Andy Yan
2023-11-14 11:29 ` [PATCH 10/11] drm/rockchip: vop2: Add debugfs support Andy Yan
2023-11-14 11:29 ` [PATCH 11/11] arm64: dts: rockchip: Add vop on rk3588 Andy Yan
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=b8605ecb-0244-4ff7-8338-759011dee1b3@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=chris.obbard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
/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