[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170160265549.1305159.13000009091015495983.b4-ty@linaro.org>
Date: Sun, 3 Dec 2023 14:26:27 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: freedreno@...ts.freedesktop.org, Rob Clark <robdclark@...il.com>,
Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Archit Taneja <architt@...eaurora.org>,
Chandan Uddaraju <chandanu@...eaurora.org>,
Jeykumar Sankaran <jsanka@...eaurora.org>,
Rajesh Yadav <ryadav@...eaurora.org>,
Abhinav Kumar <quic_abhinavk@...cinc.com>
Cc: dri-devel@...ts.freedesktop.org, quic_jesszhan@...cinc.com,
quic_parellan@...cinc.com, nespera@...lia.com,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] drm/msm/dpu: fail dpu_plane_atomic_check() based on mdp clk limits
On Mon, 11 Sep 2023 15:16:26 -0700, Abhinav Kumar wrote:
> Currently, dpu_plane_atomic_check() does not check whether the
> plane can process the image without exceeding the per chipset
> limits for MDP clock. This leads to underflow issues because the
> SSPP is not able to complete the processing for the data rate of
> the display.
>
> Fail the dpu_plane_atomic_check() if the SSPP cannot process the
> image without exceeding the MDP clock limits.
>
> [...]
Applied, thanks!
[2/2] drm/msm/dpu: try multirect based on mdp clock limits
https://gitlab.freedesktop.org/lumag/msm/-/commit/e6c0de5f4450
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Powered by blists - more mailing lists