From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 2/3] drm/msm/dpu: allow using two SSPP blocks for a single plane
Date: Wed, 11 Dec 2024 13:51:51 -0800 [thread overview]
Message-ID: <160151f0-9cc6-40f6-9f53-466185835e4d@quicinc.com> (raw)
In-Reply-To: <20241130-dpu-virtual-wide-v7-2-991053fcf63c@linaro.org>
On 11/29/2024 5:55 PM, Dmitry Baryshkov wrote:
> Virtual wide planes give high amount of flexibility, but it is not
> always enough:
>
> In parallel multirect case only the half of the usual width is supported
> for tiled formats. Thus the whole width of two tiled multirect
> rectangles can not be greater than max_linewidth, which is not enough
> for some platforms/compositors.
>
> Another example is as simple as wide YUV plane. YUV planes can not use
> multirect, so currently they are limited to max_linewidth too.
>
> Now that the planes are fully virtualized, add support for allocating
> two SSPP blocks to drive a single DRM plane. This fixes both mentioned
> cases and allows all planes to go up to 2*max_linewidth (at the cost of
> making some of the planes unavailable to the user).
>
Overall looks so much cleaner after unification!
One small nit below,
You can still have,
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
Note: we have started testing this series with sc7180 CrOS, and will
report our findings/ give tested-by this week.
<snip>
> +static bool dpu_plane_try_multirect_parallel(struct dpu_sw_pipe *pipe, struct dpu_sw_pipe_cfg *pipe_cfg,
> + struct dpu_sw_pipe *r_pipe, struct dpu_sw_pipe_cfg *r_pipe_cfg,
> + struct dpu_hw_sspp *sspp, const struct msm_format *fmt,
> + uint32_t max_linewidth)
> +{
> + r_pipe->sspp = NULL;
> +
> + pipe->multirect_index = DPU_SSPP_RECT_SOLO;
> + pipe->multirect_mode = DPU_SSPP_MULTIRECT_NONE;
> +
> + r_pipe->multirect_index = DPU_SSPP_RECT_SOLO;
> + r_pipe->multirect_mode = DPU_SSPP_MULTIRECT_NONE;
> +
There are two places where the multirect_index and multirect_mode are
reset. Would it be better to just have a small api
dpu_plane_reset_multirect() and do this there?
next prev parent reply other threads:[~2024-12-11 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 1:55 [PATCH v7 0/3] drm/msm/dpu: support virtual wide planes Dmitry Baryshkov
2024-11-30 1:55 ` [PATCH v7 1/3] drm/msm/dpu: add support for virtual planes Dmitry Baryshkov
2024-11-30 1:55 ` [PATCH v7 2/3] drm/msm/dpu: allow using two SSPP blocks for a single plane Dmitry Baryshkov
2024-12-11 21:51 ` Abhinav Kumar [this message]
2024-12-11 22:24 ` Dmitry Baryshkov
2024-12-11 22:38 ` Abhinav Kumar
2024-12-11 22:40 ` Dmitry Baryshkov
2024-11-30 1:55 ` [PATCH v7 3/3] drm/msm/dpu: include SSPP allocation state into the dumped state Dmitry Baryshkov
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=160151f0-9cc6-40f6-9f53-466185835e4d@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®