From: Harry Wentland <harry.wentland@amd.com>
To: Carlos Bilbao <carlos.bilbao@amd.com>,
sunpeng.li@amd.com, Rodrigo.Siqueira@amd.com
Cc: aric.cyr@amd.com, Xinhui.Pan@amd.com,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
alexander.deucher@amd.com, jun.lei@amd.com, airlied@gmail.com,
christian.koenig@amd.com, bilbao@vt.edu
Subject: Re: [PATCH] drm/amd/display: Amend descriptions within enum pipe_split_policy
Date: Tue, 8 Nov 2022 14:45:21 -0500 [thread overview]
Message-ID: <0fd9044b-d0c9-5d93-3d5d-8c6baaf695fd@amd.com> (raw)
In-Reply-To: <20221107143715.279841-1-carlos.bilbao@amd.com>
On 11/7/22 09:37, Carlos Bilbao wrote:
> Correct descriptions of two last fields of enum pipe_split_policy, updating
> comments with proper field names.
>
> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> ---
> drivers/gpu/drm/amd/display/dc/dc.h | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/dc/dc.h b/drivers/gpu/drm/amd/display/dc/dc.h
> index bfc5474c0f4c..277631a899d8 100644
> --- a/drivers/gpu/drm/amd/display/dc/dc.h
> +++ b/drivers/gpu/drm/amd/display/dc/dc.h
> @@ -457,15 +457,16 @@ enum pipe_split_policy {
> MPC_SPLIT_DYNAMIC = 0,
>
> /**
> - * @MPC_SPLIT_DYNAMIC: Avoid pipe split, which means that DC will not
> + * @MPC_SPLIT_AVOID: Avoid pipe split, which means that DC will not
> * try any sort of split optimization.
> */
> MPC_SPLIT_AVOID = 1,
>
> /**
> - * @MPC_SPLIT_DYNAMIC: With this option, DC will only try to optimize
> - * the pipe utilization when using a single display; if the user
> - * connects to a second display, DC will avoid pipe split.
> + * @MPC_SPLIT_AVOID_MULT_DISP: With this option, DC will only try
> + * to optimize the pipe utilization when using a single display;
> + * if the user connects to a second display, DC will avoid pipe
> + * split.
> */
> MPC_SPLIT_AVOID_MULT_DISP = 2,
> };
prev parent reply other threads:[~2022-11-08 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 14:37 Carlos Bilbao
2022-11-08 16:24 ` Alex Deucher
2022-11-08 19:45 ` Harry Wentland [this message]
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=0fd9044b-d0c9-5d93-3d5d-8c6baaf695fd@amd.com \
--to=harry.wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aric.cyr@amd.com \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jun.lei@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunpeng.li@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
all inboxes | Powered by JetHome®