[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ay5hbnqqjhopaqof6z7j2rzm2bc6xa2vbzan2ak3if6wzmyip2@kqh7gtrajnm2>
Date: Tue, 10 Dec 2024 03:01:38 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Andy Yan <andyshrk@....com>
Cc: Heiko Stübner <heiko@...ech.de>,
Daniel Semkowicz <dse@...umatec.com>, Diederik de Haas <didi.debian@...ow.org>,
andy.yan@...k-chips.com, Laurent.pinchart@...asonboard.com, andrzej.hajda@...el.com,
conor+dt@...nel.org, devicetree@...r.kernel.org, dri-devel@...ts.freedesktop.org,
jernej.skrabec@...il.com, jonas@...boo.se, krzk+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, neil.armstrong@...aro.org,
quentin.schulz@...rry.de, rfoss@...nel.org, robh@...nel.org, tzimmermann@...e.de
Subject: Re: [PATCH v3 0/3] drm/rockchip: Add driver for the new DSI2
controller
On Tue, Dec 10, 2024 at 08:50:51AM +0800, Andy Yan wrote:
>
>
> Hi,
>
> At 2024-12-10 07:12:26, "Heiko Stübner" <heiko@...ech.de> wrote:
> >Am Montag, 9. Dezember 2024, 17:11:03 CET schrieb Diederik de Haas:
> >> Hi,
> >>
> >> On Mon Dec 9, 2024 at 4:06 PM CET, Daniel Semkowicz wrote:
> >> > On 03.12.24 21:54, Heiko Stuebner wrote:
> >> > > This series adds a bridge and glue driver for the DSI2 controller found
> >> > > in the rk3588 soc from Rockchip, that is based on a Synopsis IP block.
> >> > >
> >> >
> >> > I did more tests with different LVDS displays. I tested following
> >> > configurations with DSI/LVDS bridge:
> >> > - 1024x600@...01
> >> > - 1024x768@...02
> >> > - 1280x800@...07
> >> > - 1366x768@...06
> >> >
> >> > All of them worked without issues, except 1366x768.
> >> > With this resolution, video is blurry, and offset incorrectly
> >> > to the left. There are also repeating errors on the console:
> >> >
> >> > rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp3
> >> >
> >> > In correct operation with other resolutions, there is no error.
> >> > I am not sure if this is a problem in your series or rather in VOP2
> >> > driver.
> >
> >This really sounds like something is wrong on the vop side.
> >The interrupt is part of the vop, the divisable by 4 things likely too.
>
> This is a hardware limitation on vop side:
> The horizontal resolution must be 4 pixel aligned.
Then mode_valid() and atomic_check() must reject modes that don't fit.
>
>
>
--
With best wishes
Dmitry
Powered by blists - more mailing lists