From: Harry Wentland <harry.wentland@amd.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>,
Aurabindo Pillai <aurabindo.pillai@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Subject: Re: [PATCH 2/3] drm/amd/display: Enable new commit sequence only for DCN32x
Date: Tue, 11 Oct 2022 18:08:10 -0400 [thread overview]
Message-ID: <2ed258e5-8b6f-930b-e48a-a4222dee1154@amd.com> (raw)
In-Reply-To: <20221011181140.94595-3-Rodrigo.Siqueira@amd.com>
On 2022-10-11 14:11, Rodrigo Siqueira wrote:
> Change commit sequence might impact multiple ASICs; for this reason, it
> is better to run it only on DCN32x for the first set of validation.
> After we get more confident about this change, we should expand it to
> all ASICs.
>
> Cc: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Cc: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> Co-developed-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> Signed-off-by: Aurabindo Pillai <aurabindo.pillai@amd.com>
> ---
> drivers/gpu/drm/amd/display/dc/core/dc.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
> index ad3aafb73cba..21d20900cfe3 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
> @@ -1913,6 +1913,13 @@ bool dc_commit_state(struct dc *dc, struct dc_state *context)
> enum dc_status result = DC_ERROR_UNEXPECTED;
> int i;
>
> + /* TODO: Enable the new commit sequence for all ASICs */
> + if (dc->ctx->asic_id.chip_family == AMDGPU_FAMILY_GC_11_0_0 ||
> + dc->ctx->asic_id.chip_family == AMDGPU_FAMILY_GC_11_0_1) {
Why not check that dc_ctx->dce_version == DCN_VERSION_3_2?
I don't like using the family ID in DC unless we have a good
reason to.
> + result = dc_commit_streams(dc, context->streams, context->stream_count);
Wasn't this function initially intended as a crutch for other OSes
that couldn't use dc_commit_state directly for some reasons?
I'm not sure this change is moving into the right direction, at least
not without a much more detailed explanation of why dc_commit_streams
and dc_update_planes_and_streams are the better solution.
Harry
> + return result == DC_OK;
> + }
> +
> if (!context_changed(dc, context))
> return DC_OK;
>
> @@ -3898,6 +3905,15 @@ void dc_commit_updates_for_stream(struct dc *dc,
> struct dc_context *dc_ctx = dc->ctx;
> int i, j;
>
> + /* TODO: Enable the new commit sequence for all ASICs */
> + if (dc->ctx->asic_id.chip_family == AMDGPU_FAMILY_GC_11_0_0 ||
> + dc->ctx->asic_id.chip_family == AMDGPU_FAMILY_GC_11_0_1) {
> + dc_update_planes_and_stream(dc, srf_updates,
> + surface_count, stream,
> + stream_update);
> + return;
> + }
> +
> stream_status = dc_stream_get_status(stream);
> context = dc->current_state;
>
next prev parent reply other threads:[~2022-10-11 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:11 [PATCH 0/3] Update DC commit sequence Rodrigo Siqueira
2022-10-11 18:11 ` [PATCH 1/3] drm/amd/display: Add functions for new " 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 [this message]
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=2ed258e5-8b6f-930b-e48a-a4222dee1154@amd.com \
--to=harry.wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.