From: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
To: <amd-gfx@lists.freedesktop.org>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: [PATCH 0/3] Update DC commit sequence
Date: Tue, 11 Oct 2022 14:11:37 -0400 [thread overview]
Message-ID: <20221011181140.94595-1-Rodrigo.Siqueira@amd.com> (raw)
This patchset introduces the basic infrastructure to change our display
commit sequence to make it more robust and flexible for handling some
display features. Current, amdgpu_dm tries to commit a validation state
directly into update_planes and commit_streams. However, we want to
avoid committing the state directly into DC; instead, we only want to
pass streams/plane pointers into DC and let it manage the commit state
entirely. This behavior is more future-proof because it keeps the state
manipulation inside DC, which can benefit some specific features that
might want to play with the context state.
Cc: Daniel Wheeler <daniel.wheeler@amd.com>
Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Cc: Harry Wentland <harry.wentland@amd.com>
Aurabindo Pillai (1):
drm/amd/display: Move dc_state copy in commit_tail after
dc_commit_state
Rodrigo Siqueira (2):
drm/amd/display: Add functions for new DC commit sequence
drm/amd/display: Enable new commit sequence only for DCN32x
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 17 +-
drivers/gpu/drm/amd/display/dc/core/dc.c | 108 ++++++++++
.../gpu/drm/amd/display/dc/core/dc_resource.c | 204 +++++++++++++++++-
drivers/gpu/drm/amd/display/dc/dc.h | 6 +
drivers/gpu/drm/amd/display/dc/dc_stream.h | 11 +-
5 files changed, 333 insertions(+), 13 deletions(-)
--
2.35.1
next reply other threads:[~2022-10-11 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:11 Rodrigo Siqueira [this message]
2022-10-11 18:11 ` [PATCH 1/3] drm/amd/display: Add functions for new DC commit sequence Rodrigo Siqueira
2022-10-11 18:47 ` Harry Wentland
2022-10-11 18:11 ` [PATCH 2/3] drm/amd/display: Enable new commit sequence only for DCN32x Rodrigo Siqueira
2022-10-11 22:08 ` Harry Wentland
2022-10-11 18:11 ` [PATCH 3/3] drm/amd/display: Move dc_state copy in commit_tail after dc_commit_state Rodrigo Siqueira
2022-10-11 22:03 ` Harry Wentland
2022-10-11 18:52 ` [PATCH 0/3] Update DC commit sequence Wheeler, Daniel
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=20221011181140.94595-1-Rodrigo.Siqueira@amd.com \
--to=rodrigo.siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.wheeler@amd.com \
--cc=harry.wentland@amd.com \
--cc=nicholas.kazlauskas@amd.com \
/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