Re: [PATCH RESEND] drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels

From: Aditya Garg <gargaditya08@live.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "harry.wentland@amd.com" <harry.wentland@amd.com>,
	"sunpeng.li@amd.com" <sunpeng.li@amd.com>,
	"Rodrigo.Siqueira@amd.com" <Rodrigo.Siqueira@amd.com>,
	"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
	"christian.koenig@amd.com" <christian.koenig@amd.com>,
	"Xinhui.Pan@amd.com" <Xinhui.Pan@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
	"evan.quan@amd.com" <evan.quan@amd.com>,
	"stylon.wang@amd.com" <stylon.wang@amd.com>,
	"wesley.chalmers@amd.com" <wesley.chalmers@amd.com>,
	"qingqing.zhuo@amd.com" <qingqing.zhuo@amd.com>,
	"George.Shen@amd.com" <George.Shen@amd.com>,
	"roman.li@amd.com" <roman.li@amd.com>,
	"solomon.chiu@amd.com" <solomon.chiu@amd.com>,
	"Aurabindo.Pillai@amd.com" <Aurabindo.Pillai@amd.com>,
	"wayne.lin@amd.com" <wayne.lin@amd.com>,
	"mikita.lipski@amd.com" <mikita.lipski@amd.com>,
	"Bhawanpreet.Lakha@amd.com" <Bhawanpreet.Lakha@amd.com>,
	"agustin.gutierrez@amd.com" <agustin.gutierrez@amd.com>,
	"pavle.kotarac@amd.com" <pavle.kotarac@amd.com>,
	Aun-Ali Zaidi <admin@kodeit.net>,
	Orlando Chamberlain <redecorating@protonmail.com>
Subject: Re: [PATCH RESEND] drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina panels
Date: Fri, 28 Jan 2022 13:06:52 +0000	[thread overview]
Message-ID: <58B7B0D4-BA3B-43EA-9F54-06CCEB7EF833@live.com> (raw)
In-Reply-To: <CADnq5_OLpgEJjpN5y9b3gNwCmvdfNTA=puUv8UjOCDH96JgvOQ@mail.gmail.com>

Hi Alex

> On 27-Jan-2022, at 11:06 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
> 
> C style comments please.
Shall be fixed in v2
>  I'll let one of the display guys comment on
> the rest of the patch.  Seems reasonable, we have a similar quirk for
> the Apple MBP 2017 15" Retina panel later in this function.  Could you
> move this next to the other quirk?
I guess moving it next to the other quirk may break the functionality of this quirk, cause the MBP 2018 one involves stuff regarding firmware revision as well. The original patch applies the quirk after the following lines of the code :-

	core_link_read_dpcd(
		link,
		DP_SINK_HW_REVISION_START,
		(uint8_t *)&dp_hw_fw_revision,
		sizeof(dp_hw_fw_revision));

	link->dpcd_caps.sink_hw_revision =
		dp_hw_fw_revision.ieee_hw_rev;

	memmove(
		link->dpcd_caps.sink_fw_revision,
		dp_hw_fw_revision.ieee_fw_rev,
		sizeof(dp_hw_fw_revision.ieee_fw_rev));

Which seem to related to the firmware stuff. Moving it along with the 2017 quirk doesn't sound right to me, as this shall move the quirk BEFORE these lines of code instead. Maybe the author also knowingly added the quirk after these lines of code?

As a workaround, could we move the 2017 quirk later, instead of moving the 2018 quirk before? This sounds more logical to me.

Regards
Aditya