From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: 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: [RFT PATCH v2 0/4] drm/msm/dpu: enable writeback on the other platforms
Date: Sun, 3 Dec 2023 03:31:59 +0300 [thread overview]
Message-ID: <20231203003203.1293087-1-dmitry.baryshkov@linaro.org> (raw)
I was not able to test it on my own, this is a call for testing for the
owners of these platforms. The git version of modetest now fully
supports writeback.
Use libdrm >= 2.4.117, run modetest -ac to determine the writeback
connector, cat /sys/kernel/debug/dri/0/state to determine
spare CRTC and plane, then run something like:
modetest -M msm -a -s 36@85:1024x768 -o test.d -P 79@85:1024x768
where 36 is the Writeback connector id, 85 is CRTC and 79 is the plane.
Then press Enter and check the test.d file for the raw image dump.
Changes since v1:
- Fixed the DPU_CLK_CTRL_WB2 definition
Dmitry Baryshkov (4):
drm/msm/dpu: enable writeback on SM8150
drm/msm/dpu: enable writeback on SC8108X
drm/msm/dpu: enable writeback on SM6125
drm/msm/dpu: enable writeback on SM6350
.../drm/msm/disp/dpu1/catalog/dpu_5_0_sm8150.h | 18 ++++++++++++++++++
.../msm/disp/dpu1/catalog/dpu_5_1_sc8180x.h | 18 ++++++++++++++++++
.../drm/msm/disp/dpu1/catalog/dpu_5_4_sm6125.h | 18 ++++++++++++++++++
.../drm/msm/disp/dpu1/catalog/dpu_6_4_sm6350.h | 18 ++++++++++++++++++
4 files changed, 72 insertions(+)
--
2.39.2
next reply other threads:[~2023-12-03 0:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 0:31 Dmitry Baryshkov [this message]
2023-12-03 0:32 ` [RFT PATCH v2 1/4] drm/msm/dpu: enable writeback on SM8150 Dmitry Baryshkov
2023-12-05 11:46 ` kernel test robot
2023-12-05 13:32 ` kernel test robot
2023-12-13 21:13 ` Abhinav Kumar
2023-12-03 0:32 ` [RFT PATCH v2 2/4] drm/msm/dpu: enable writeback on SC8108X Dmitry Baryshkov
2023-12-05 18:50 ` kernel test robot
2023-12-13 21:18 ` Abhinav Kumar
2023-12-21 23:36 ` Marijn Suijten
2023-12-03 0:32 ` [RFT PATCH v2 3/4] drm/msm/dpu: enable writeback on SM6125 Dmitry Baryshkov
2023-12-13 21:19 ` Abhinav Kumar
2023-12-03 0:32 ` [RFT PATCH v2 4/4] drm/msm/dpu: enable writeback on SM6350 Dmitry Baryshkov
2023-12-19 15:39 ` Luca Weiss
2024-01-24 8:00 ` Luca Weiss
2023-12-12 0:30 ` [RFT PATCH v2 0/4] drm/msm/dpu: enable writeback on the other platforms Abhinav Kumar
2023-12-12 6:23 ` Dmitry Baryshkov
2023-12-13 21:09 ` Abhinav Kumar
2024-09-05 3:33 ` 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=20231203003203.1293087-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--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;
as well as URLs for NNTP newsgroup(s).