From: Jani Nikula <jani.nikula@intel.com>
To: "Zuo, Jerry" <Jerry.Zuo@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"lyude@redhat.com" <lyude@redhat.com>,
"imre.deak@intel.com" <imre.deak@intel.com>,
"simona@ffwll.ch" <simona@ffwll.ch>
Cc: "Wentland, Harry" <Harry.Wentland@amd.com>,
"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
"Lin, Wayne" <Wayne.Lin@amd.com>
Subject: RE: [PATCH v4 0/2] Refactor MST DSC Determination Policy
Date: Fri, 22 Nov 2024 11:25:46 +0200 [thread overview]
Message-ID: <87jzcvzkkl.fsf@intel.com> (raw)
In-Reply-To: <IA1PR12MB90631D65960DEFFCE3CFD4C0E5222@IA1PR12MB9063.namprd12.prod.outlook.com>
On Thu, 21 Nov 2024, "Zuo, Jerry" <Jerry.Zuo@amd.com> wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Lyude, Jani, Imre, Simona:
>
> Please kindly review the patch series at your convenient
> time. Thanks.
There's still way too much going on in one patch. It's too hard to do
proper detailed review on this. I don't have that kind of time to spend.
If you were to get a regression report on this maybe a year down the
line when it hits major distros, what are your chances of pinpointing
what went wrong? What are your chances of quickly debugging and fixing
it? I'm thinking slim.
MST is too complicated to trap ourselves in that scenario.
Please find a way to do incremental refactoring first to support your
functional changes.
BR,
Jani.
>
> Regards,
> Jerry
>
>> -----Original Message-----
>> From: Fangzhi Zuo <Jerry.Zuo@amd.com>
>> Sent: Friday, November 8, 2024 12:42 PM
>> To: dri-devel@lists.freedesktop.org; amd-gfx@lists.freedesktop.org; intel-
>> gfx@lists.freedesktop.org; lyude@redhat.com; jani.nikula@intel.com;
>> imre.deak@intel.com; simona@ffwll.ch; Lin, Wayne <Wayne.Lin@amd.com>
>> Cc: Wentland, Harry <Harry.Wentland@amd.com>; Siqueira, Rodrigo
>> <Rodrigo.Siqueira@amd.com>; Zuo, Jerry <Jerry.Zuo@amd.com>
>> Subject: [PATCH v4 0/2] Refactor MST DSC Determination Policy
>>
>> The patch series is to refactor existing dsc determination policy for dsc
>> decompression and dsc passthrough given a mst output port.
>>
>> Original routine was written based on different peer device types which is not
>> accurate and shows difficulty when expanding support of products that do not fully
>> comply with DP specs.
>>
>> To make the routine more accurate and generic, the series includes below changes:
>> 1. Refactor MST DSC determination policy solely based on
>> topology connection status and dsc dpcd capability info.
>> 2. Dependency changes required for each vendor due to interface change.
>>
>> v2: split original single patch into two
>> v3: rebase against the latest code
>> v4: fix a ci issue
>>
>> Fangzhi Zuo (2):
>> drm/display/dsc: Refactor DRM MST DSC Determination Policy
>> drm/display/dsc: MST DSC Interface Change
>>
>> .../amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 2 +-
>> .../amd/display/amdgpu_dm/amdgpu_dm_helpers.c | 20 +-
>> .../display/amdgpu_dm/amdgpu_dm_mst_types.c | 28 +-
>> drivers/gpu/drm/display/drm_dp_mst_topology.c | 261 ++++++++----------
>> drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
>> drivers/gpu/drm/i915/display/intel_dp_mst.c | 3 +-
>> include/drm/display/drm_dp_mst_helper.h | 9 +-
>> 7 files changed, 147 insertions(+), 178 deletions(-)
>>
>> --
>> 2.43.0
>
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-11-22 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 17:41 [PATCH v4 0/2] Refactor MST DSC Determination Policy Fangzhi Zuo
2024-11-08 17:41 ` [PATCH v4 1/2] drm/display/dsc: Refactor DRM " Fangzhi Zuo
2024-11-08 17:41 ` [PATCH v4 2/2] drm/display/dsc: MST DSC Interface Change Fangzhi Zuo
2024-11-08 18:21 ` ✗ Fi.CI.CHECKPATCH: warning for Refactor MST DSC Determination Policy (rev3) Patchwork
2024-11-08 18:21 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-08 18:37 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-08 19:48 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-11-21 23:10 ` [PATCH v4 0/2] Refactor MST DSC Determination Policy Zuo, Jerry
2024-11-22 9:25 ` Jani Nikula [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=87jzcvzkkl.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Harry.Wentland@amd.com \
--cc=Jerry.Zuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lyude@redhat.com \
--cc=simona@ffwll.ch \
/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