From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kalyan Thota <quic_kalyant@quicinc.com>,
dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, robdclark@chromium.org,
dianders@chromium.org, swboyd@chromium.org,
quic_vpolimer@quicinc.com, quic_abhinavk@quicinc.com,
marijn.suijten@somainline.org
Subject: Re: [PATCH 0/3] Reserve dspps based on user request
Date: Mon, 30 Jan 2023 21:18:30 +0200 [thread overview]
Message-ID: <31661b18-8519-cadb-0c56-6a1fa34633b2@linaro.org> (raw)
In-Reply-To: <1675092092-26412-1-git-send-email-quic_kalyant@quicinc.com>
On 30/01/2023 17:21, Kalyan Thota wrote:
> This series will enable color features on sc7280 target which has primary panel as eDP
>
> The series removes dspp allocation based on encoder type and allows the dspp reservation
> based on user request via ctm.
>
> The series will release/reserve the dpu resources when ever there is a topology change
> to suit the new requirements.
Nit: the subject of the cover letter should include the version, if you
are including one into the individual patches Subject.
>
> Kalyan Thota (3):
> drm/msm/disp/dpu1: clear dspp reservations in rm release
> drm/msm/disp/dpu1: add dspps into reservation if there is a ctm
> request
> drm/msm/disp/dpu1: reserve the resources on topology change
>
> drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.h | 1 +
> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 54 +++++++++++++++++++++++------
> drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 4 ++-
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 2 +-
> drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c | 6 ++--
> 5 files changed, 50 insertions(+), 17 deletions(-)
>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-01-30 19:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:21 [PATCH 0/3] Reserve dspps based on user request Kalyan Thota
2023-01-30 15:21 ` [v1 1/3] drm/msm/disp/dpu1: clear dspp reservations in rm release Kalyan Thota
2023-02-01 11:10 ` Marijn Suijten
2023-02-01 11:21 ` Marijn Suijten
2023-01-30 15:21 ` [v1 2/3] drm/msm/disp/dpu1: add dspps into reservation if there is a ctm request Kalyan Thota
2023-01-30 18:36 ` Dmitry Baryshkov
2023-02-01 11:16 ` Marijn Suijten
2023-02-01 11:26 ` Marijn Suijten
2023-02-01 13:49 ` Dmitry Baryshkov
2023-02-01 13:48 ` Dmitry Baryshkov
2023-02-01 15:10 ` Marijn Suijten
2023-01-30 15:21 ` [v1 3/3] drm/msm/disp/dpu1: reserve the resources on topology change Kalyan Thota
2023-01-30 19:17 ` Dmitry Baryshkov
2023-02-02 4:22 ` kernel test robot
2023-02-02 14:08 ` kernel test robot
2023-01-30 19:18 ` Dmitry Baryshkov [this message]
2023-02-01 11:01 ` [PATCH 0/3] Reserve dspps based on user request Marijn Suijten
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 10:15 Kalyan Thota
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=31661b18-8519-cadb-0c56-6a1fa34633b2@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.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=quic_abhinavk@quicinc.com \
--cc=quic_kalyant@quicinc.com \
--cc=quic_vpolimer@quicinc.com \
--cc=robdclark@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).