From: Aurabindo Pillai <aurabindo.pillai@amd.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Rouven Czerwinski <rouven@czerwinskis.de>
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rouven Czerwinski" <r.czerwinski@pengutronix.de>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org, kernel@pengutronix.de
Subject: Re: [PATCH] drm/amd/display: remove unused function dc_link_perform_link_training
Date: Mon, 10 May 2021 19:49:16 -0400 [thread overview]
Message-ID: <97fc07d6-dcfa-8d04-7658-311df58745e5@amd.com> (raw)
In-Reply-To: <20210510213356.ddqnz4yyqo4ngkp4@outlook.office365.com>
On 2021-05-10 5:33 p.m., Rodrigo Siqueira wrote:
> LGTM,
>
> Jay, any comment?
None, LGTM, and this applied already.
>
> Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
>
> On 05/08, Rouven Czerwinski wrote:
>> This function is not used anywhere, remove it. It was added in
>> 40dd6bd376a4 ("drm/amd/display: Linux Set/Read link rate and lane count
>> through debugfs") and moved in fe798de53a7a ("drm/amd/display: Move link
>> functions from dc to dc_link"), but a user is missing.
>>
>> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
>> ---
>> drivers/gpu/drm/amd/display/dc/core/dc_link.c | 13 -------------
>> drivers/gpu/drm/amd/display/dc/dc_link.h | 3 ---
>> 2 files changed, 16 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_link.c b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
>> index 3fb0cebd6938..55c5cf2264b3 100644
>> --- a/drivers/gpu/drm/amd/display/dc/core/dc_link.c
>> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
>> @@ -3553,19 +3553,6 @@ void dc_link_set_drive_settings(struct dc *dc,
>> dc_link_dp_set_drive_settings(dc->links[i], lt_settings);
>> }
>>
>> -void dc_link_perform_link_training(struct dc *dc,
>> - struct dc_link_settings *link_setting,
>> - bool skip_video_pattern)
>> -{
>> - int i;
>> -
>> - for (i = 0; i < dc->link_count; i++)
>> - dc_link_dp_perform_link_training(
>> - dc->links[i],
>> - link_setting,
>> - skip_video_pattern);
>> -}
>> -
>> void dc_link_set_preferred_link_settings(struct dc *dc,
>> struct dc_link_settings *link_setting,
>> struct dc_link *link)
>> diff --git a/drivers/gpu/drm/amd/display/dc/dc_link.h b/drivers/gpu/drm/amd/display/dc/dc_link.h
>> index fc5622ffec3d..45c927cd27ab 100644
>> --- a/drivers/gpu/drm/amd/display/dc/dc_link.h
>> +++ b/drivers/gpu/drm/amd/display/dc/dc_link.h
>> @@ -363,9 +363,6 @@ bool dc_link_is_hdcp22(struct dc_link *link, enum signal_type signal);
>> void dc_link_set_drive_settings(struct dc *dc,
>> struct link_training_settings *lt_settings,
>> const struct dc_link *link);
>> -void dc_link_perform_link_training(struct dc *dc,
>> - struct dc_link_settings *link_setting,
>> - bool skip_video_pattern);
>> void dc_link_set_preferred_link_settings(struct dc *dc,
>> struct dc_link_settings *link_setting,
>> struct dc_link *link);
>> --
>> 2.31.1
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx@lists.freedesktop.org
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=04%7C01%7CRodrigo.Siqueira%40amd.com%7C9724972184d64ad6e7e008d913010665%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637561717696066502%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=vUFEeBJwjTDnI9l8MGDiW8%2FoX7LINZi%2FfD4A004QfLs%3D&reserved=0
>
--
Regards,
Aurabindo Pillai
prev parent reply other threads:[~2021-05-10 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 18:19 Rouven Czerwinski
2021-05-10 20:53 ` Alex Deucher
2021-05-10 21:33 ` Rodrigo Siqueira
2021-05-10 23:49 ` Aurabindo Pillai [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=97fc07d6-dcfa-8d04-7658-311df58745e5@amd.com \
--to=aurabindo.pillai@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=r.czerwinski@pengutronix.de \
--cc=rouven@czerwinskis.de \
--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®