Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Sui Jingfeng <sui.jingfeng@linux.dev>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Marijn Suijten <marijn.suijten@somainline.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	freedreno@lists.freedesktop.org
Subject: Re: [v4,08/13] drm/msm/dpu: add support for virtual planes
Date: Thu, 14 Mar 2024 16:04:33 +0800	[thread overview]
Message-ID: <58cf7cb4-7d78-4d3d-9958-1c59b7f16379@linux.dev> (raw)
In-Reply-To: <20240314000216.392549-9-dmitry.baryshkov@linaro.org>

Hi,


On 2024/3/14 08:02, Dmitry Baryshkov wrote:


[...]


>   
> +/**
> + * dpu_rm_reserve_sspp - Reserve the required SSPP for the provided CRTC
> + * @rm: DPU Resource Manager handle
> + * @global_state: private global state
> + * @crtc: DRM CRTC handle
> + * @reqs: SSPP required features
> + */
> +struct dpu_hw_sspp *dpu_rm_reserve_sspp(struct dpu_rm *rm,
> +					struct dpu_global_state *global_state,
> +					struct drm_crtc *crtc,
> +					struct dpu_rm_sspp_requirements *reqs);
> +
> +/**
> + * dpu_rm_release_all_sspp - Given the CRTC, release all SSPP
> + *	blocks previously reserved for that use case.
> + * @rm: DPU Resource Manager handle
> + * @crtc: DRM CRTC handle
> + * @Return: 0 on Success otherwise -ERROR
> + */

But this function do not return any value, right?


> +void dpu_rm_release_all_sspp(struct dpu_global_state *global_state,
> +			     struct drm_crtc *crtc);
> +
>   /**
>    * Get hw resources of the given type that are assigned to this encoder.
>    */

-- 
Best regards,
Sui


  reply	other threads:[~2024-03-14  8:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  0:02 [PATCH v4 00/13] drm/msm/dpu: support virtual wide planes Dmitry Baryshkov
2024-03-14  0:02 ` [PATCH v4 01/13] drm/msm/dpu: take plane rotation into account for " Dmitry Baryshkov
2024-05-30 22:51   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 02/13] drm/msm/dpu: use drm_rect_fp_to_int() Dmitry Baryshkov
2024-05-30 23:14   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 03/13] drm/msm/dpu: move pstate->pipe initialization to dpu_plane_atomic_check Dmitry Baryshkov
2024-05-31  0:28   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 04/13] drm/msm/dpu: drop virt_formats from SSPP subblock configuration Dmitry Baryshkov
2024-05-31  0:32   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 05/13] drm/msm/dpu: move scaling limitations out of the hw_catalog Dmitry Baryshkov
2024-05-31  1:02   ` Abhinav Kumar
2024-05-31  8:16     ` Dmitry Baryshkov
2024-05-31 19:20       ` Abhinav Kumar
2024-05-31 19:45         ` Dmitry Baryshkov
2024-03-14  0:02 ` [PATCH v4 06/13] drm/msm/dpu: split dpu_plane_atomic_check() Dmitry Baryshkov
2024-06-05 23:19   ` Abhinav Kumar
2024-06-05 23:32     ` Dmitry Baryshkov
2024-06-05 23:47       ` Abhinav Kumar
2024-06-06  8:53         ` Dmitry Baryshkov
2024-06-06  8:54           ` Dmitry Baryshkov
2024-03-14  0:02 ` [PATCH v4 07/13] drm/msm/dpu: move rot90 checking to dpu_plane_atomic_check_pipe() Dmitry Baryshkov
2024-06-05 23:34   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 08/13] drm/msm/dpu: add support for virtual planes Dmitry Baryshkov
2024-03-14  8:04   ` Sui Jingfeng [this message]
2024-06-06 22:21   ` Abhinav Kumar
2024-06-07  7:16     ` Dmitry Baryshkov
2024-06-07 19:22       ` Abhinav Kumar
2024-06-07 21:10         ` Dmitry Baryshkov
2024-06-07 21:39           ` Abhinav Kumar
2024-06-07 22:26             ` Dmitry Baryshkov
2024-06-07 23:55               ` Abhinav Kumar
2024-06-08  0:57                 ` Dmitry Baryshkov
2024-06-08  2:45                   ` Abhinav Kumar
2024-06-10 21:01                     ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 09/13] drm/msm/dpu: allow using two SSPP blocks for a single plane Dmitry Baryshkov
2024-06-10 20:19   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 10/13] drm/msm/dpu: allow sharing SSPP between planes Dmitry Baryshkov
2024-06-11 23:12   ` Abhinav Kumar
2024-06-12  9:08     ` Dmitry Baryshkov
2024-06-13  1:17       ` Abhinav Kumar
2024-06-13 10:05         ` Dmitry Baryshkov
2024-06-13 20:02           ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 11/13] drm/msm/dpu: create additional virtual planes Dmitry Baryshkov
2024-06-11 23:26   ` Abhinav Kumar
2024-03-14  0:02 ` [PATCH v4 12/13] drm/msm/dpu: allow sharing of blending stages Dmitry Baryshkov
2024-06-12  1:47   ` Abhinav Kumar
2024-06-12  8:50     ` Dmitry Baryshkov
2024-03-14  0:02 ` [PATCH v4 13/13] drm/msm/dpu: include SSPP allocation state into the dumped state Dmitry Baryshkov
2024-06-11 23:43   ` Abhinav Kumar
2024-03-14  0:04 ` [PATCH v4 00/13] 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=58cf7cb4-7d78-4d3d-9958-1c59b7f16379@linux.dev \
    --to=sui.jingfeng@linux.dev \
    --cc=airlied@gmail.com \
    --cc=andersson@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=swboyd@chromium.org \
    /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