* [v1] drm/msm/dpu: consider vertical front porch in the prefill bw calculation
@ 2020-11-25 10:02 Kalyan Thota
2020-11-25 11:24 ` Amit Pundir
0 siblings, 1 reply; 2+ messages in thread
From: Kalyan Thota @ 2020-11-25 10:02 UTC (permalink / raw)
To: y, dri-devel, linux-arm-msm, freedreno, devicetree
Cc: Kalyan Thota, linux-kernel, robdclark, seanpaul, hoegsberg,
dianders, mkrishn, travitej, nganji, swboyd, abhinavk, ddavenport,
amit.pundir, sumit.semwal
In case of panels with low vertical back porch, the prefill bw
requirement will be high as we will have less time(vbp+pw) to
fetch and fill the hw latency buffers before start of first line
in active period.
For ex:
Say hw_latency_line_buffers = 24, and if blanking vbp+pw = 10
Here we need to fetch 24 lines of data in 10 line times.
This will increase the bw to the ratio of linebuffers to blanking.
DPU hw can also fetch data during vertical front porch provided
interface prefetch is enabled. Use vfp in the prefill calculation
as dpu driver enables prefetch if the blanking is not sufficient
to fill the latency lines.
Signed-off-by: Kalyan Thota <kalyan_t@codeaurora.org>
---
drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
index 7ea90d2..315b999 100644
--- a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
+++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
@@ -151,7 +151,7 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
u64 plane_bw;
u32 hw_latency_lines;
u64 scale_factor;
- int vbp, vpw;
+ int vbp, vpw, vfp;
pstate = to_dpu_plane_state(plane->state);
mode = &plane->state->crtc->mode;
@@ -164,6 +164,7 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
fps = drm_mode_vrefresh(mode);
vbp = mode->vtotal - mode->vsync_end;
vpw = mode->vsync_end - mode->vsync_start;
+ vfp = mode->vsync_start - mode->vdisplay;
hw_latency_lines = dpu_kms->catalog->perf.min_prefill_lines;
scale_factor = src_height > dst_height ?
mult_frac(src_height, 1, dst_height) : 1;
@@ -176,7 +177,13 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
src_width * hw_latency_lines * fps * fmt->bpp *
scale_factor * mode->vtotal;
- do_div(plane_prefill_bw, (vbp+vpw));
+ if ((vbp+vpw) > hw_latency_lines)
+ do_div(plane_prefill_bw, (vbp+vpw));
+ else if ((vbp+vpw+vfp) < hw_latency_lines)
+ do_div(plane_prefill_bw, (vbp+vpw+vfp));
+ else
+ do_div(plane_prefill_bw, hw_latency_lines);
+
pstate->plane_fetch_bw = max(plane_bw, plane_prefill_bw);
}
--
2.7.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [v1] drm/msm/dpu: consider vertical front porch in the prefill bw calculation
2020-11-25 10:02 [v1] drm/msm/dpu: consider vertical front porch in the prefill bw calculation Kalyan Thota
@ 2020-11-25 11:24 ` Amit Pundir
0 siblings, 0 replies; 2+ messages in thread
From: Amit Pundir @ 2020-11-25 11:24 UTC (permalink / raw)
To: Kalyan Thota
Cc: y, dri-devel, linux-arm-msm, freedreno, dt, lkml, Rob Clark,
Sean Paul, Kristian H. Kristensen, Doug Anderson,
Krishna Manikandan, Raviteja Tamatam, nganji, Stephen Boyd,
abhinavk, ddavenport, Sumit Semwal
On Wed, 25 Nov 2020 at 15:33, Kalyan Thota <kalyan_t@codeaurora.org> wrote:
>
> In case of panels with low vertical back porch, the prefill bw
> requirement will be high as we will have less time(vbp+pw) to
> fetch and fill the hw latency buffers before start of first line
> in active period.
>
> For ex:
> Say hw_latency_line_buffers = 24, and if blanking vbp+pw = 10
> Here we need to fetch 24 lines of data in 10 line times.
> This will increase the bw to the ratio of linebuffers to blanking.
>
> DPU hw can also fetch data during vertical front porch provided
> interface prefetch is enabled. Use vfp in the prefill calculation
> as dpu driver enables prefetch if the blanking is not sufficient
> to fill the latency lines.
Tested on Xiaomi Poco F1 (sdm845).
Tested-by: Amit Pundir <amit.pundir@linaro.org>
>
> Signed-off-by: Kalyan Thota <kalyan_t@codeaurora.org>
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> index 7ea90d2..315b999 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> @@ -151,7 +151,7 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
> u64 plane_bw;
> u32 hw_latency_lines;
> u64 scale_factor;
> - int vbp, vpw;
> + int vbp, vpw, vfp;
>
> pstate = to_dpu_plane_state(plane->state);
> mode = &plane->state->crtc->mode;
> @@ -164,6 +164,7 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
> fps = drm_mode_vrefresh(mode);
> vbp = mode->vtotal - mode->vsync_end;
> vpw = mode->vsync_end - mode->vsync_start;
> + vfp = mode->vsync_start - mode->vdisplay;
> hw_latency_lines = dpu_kms->catalog->perf.min_prefill_lines;
> scale_factor = src_height > dst_height ?
> mult_frac(src_height, 1, dst_height) : 1;
> @@ -176,7 +177,13 @@ static void _dpu_plane_calc_bw(struct drm_plane *plane,
> src_width * hw_latency_lines * fps * fmt->bpp *
> scale_factor * mode->vtotal;
>
> - do_div(plane_prefill_bw, (vbp+vpw));
> + if ((vbp+vpw) > hw_latency_lines)
> + do_div(plane_prefill_bw, (vbp+vpw));
> + else if ((vbp+vpw+vfp) < hw_latency_lines)
> + do_div(plane_prefill_bw, (vbp+vpw+vfp));
> + else
> + do_div(plane_prefill_bw, hw_latency_lines);
> +
>
> pstate->plane_fetch_bw = max(plane_bw, plane_prefill_bw);
> }
> --
> 2.7.4
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-11-25 11:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-25 10:02 [v1] drm/msm/dpu: consider vertical front porch in the prefill bw calculation Kalyan Thota
2020-11-25 11:24 ` Amit Pundir
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox