Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
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 v6 4/9] drm/msm/dpu: move scaling limitations out of the hw_catalog
Date: Fri, 25 Oct 2024 16:15:34 -0700	[thread overview]
Message-ID: <be14550e-506b-4126-aa13-e983492d3cd3@quicinc.com> (raw)
In-Reply-To: <20241025-dpu-virtual-wide-v6-4-0310fd519765@linaro.org>



On 10/24/2024 5:20 PM, Dmitry Baryshkov wrote:
> Max upscale / downscale factors are constant between platforms. In
> preparation to adding support for virtual planes and allocating SSPP
> blocks on demand move max scaling factors out of the HW catalog and
> handle them in the dpu_plane directly. If any of the scaling blocks gets
> different limitations, this will have to be handled separately, after
> the plane refactoring.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 16 ----------------
>   drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h |  4 ----
>   drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c      | 16 +++++++++++++---
>   3 files changed, 13 insertions(+), 23 deletions(-)
> 


This was also R-bed in v5 and I dont see anything changed, LGTM anyway

Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>

  reply	other threads:[~2024-10-25 23:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  0:20 [PATCH v6 0/9] drm/msm/dpu: support virtual wide planes Dmitry Baryshkov
2024-10-25  0:20 ` [PATCH v6 1/9] drm/msm/dpu: use drm_rect_fp_to_int() Dmitry Baryshkov
2024-10-25  0:20 ` [PATCH v6 2/9] drm/msm/dpu: move pstate->pipe initialization to dpu_plane_atomic_check Dmitry Baryshkov
2024-10-25 19:00   ` Abhinav Kumar
2024-10-28 10:46     ` Dmitry Baryshkov
2024-10-29 20:42       ` Abhinav Kumar
2024-10-25  0:20 ` [PATCH v6 3/9] drm/msm/dpu: drop virt_formats from SSPP subblock configuration Dmitry Baryshkov
2024-10-25  0:20 ` [PATCH v6 4/9] drm/msm/dpu: move scaling limitations out of the hw_catalog Dmitry Baryshkov
2024-10-25 23:15   ` Abhinav Kumar [this message]
2024-10-25  0:20 ` [PATCH v6 5/9] drm/msm/dpu: split dpu_plane_atomic_check() Dmitry Baryshkov
2024-10-25 23:21   ` Abhinav Kumar
2024-10-25  0:20 ` [PATCH v6 6/9] drm/msm/dpu: move rot90 checking to dpu_plane_atomic_check_sspp() Dmitry Baryshkov
2024-10-29 21:00   ` Abhinav Kumar
2024-10-25  0:20 ` [PATCH v6 7/9] drm/msm/dpu: add support for virtual planes Dmitry Baryshkov
2024-10-29 21:30   ` Abhinav Kumar
2024-10-30 10:48     ` Dmitry Baryshkov
2024-10-30 19:26       ` Abhinav Kumar
2024-10-31 15:11         ` Dmitry Baryshkov
2024-10-31 15:17           ` Dmitry Baryshkov
2024-10-31 20:06           ` Abhinav Kumar
2024-10-31 21:03             ` Dmitry Baryshkov
2024-11-01 20:37               ` Abhinav Kumar
2024-11-01 20:53                 ` Dmitry Baryshkov
2024-11-01 21:27                   ` Abhinav Kumar
2024-11-01 23:30                     ` Abhinav Kumar
2024-10-25  0:20 ` [PATCH v6 8/9] drm/msm/dpu: allow using two SSPP blocks for a single plane Dmitry Baryshkov
2024-10-29 22:07   ` Abhinav Kumar
2024-10-30 10:03     ` Dmitry Baryshkov
2024-10-25  0:20 ` [PATCH v6 9/9] drm/msm/dpu: include SSPP allocation state into the dumped state Dmitry Baryshkov
2024-11-02  1:08 ` [PATCH v6 0/9] drm/msm/dpu: support virtual wide planes 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=be14550e-506b-4126-aa13-e983492d3cd3@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