[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7034316.0VBMTVartN@diego>
Date: Wed, 15 Nov 2023 00:34:07 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Andy Yan <andyshrk@....com>
Cc: hjc@...k-chips.com, dri-devel@...ts.freedesktop.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
krzysztof.kozlowski+dt@...aro.org, robh+dt@...nel.org,
devicetree@...r.kernel.org, sebastian.reichel@...labora.com,
kever.yang@...k-chips.com, chris.obbard@...labora.com,
s.hauer@...gutronix.de, Andy Yan <andy.yan@...k-chips.com>
Subject: Re: [PATCH 09/11] drm/rockchip: vop2: Add support for rk3588
Hi Andy,
Am Dienstag, 14. November 2023, 12:28:55 CET schrieb Andy Yan:
> From: Andy Yan <andy.yan@...k-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@...k-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?
Thanks
Heiko
Powered by blists - more mailing lists