From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Daniel Wheeler <Daniel.Wheeler@amd.com>
Cc: Chao-kai Wang <Stylon.Wang@amd.com>,
Sun peng Li <Sunpeng.Li@amd.com>,
Harry Wentland <Harry.Wentland@amd.com>,
Qingqing Zhuo <Qingqing.Zhuo@amd.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Roman Li <Roman.Li@amd.com>,
amd-gfx@lists.freedesktop.org,
Solomon Chiu <Solomon.Chiu@amd.com>,
Aurabindo Pillai <Aurabindo.Pillai@amd.com>,
Wayne Lin <Wayne.Lin@amd.com>,
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
Agustin Gutierrez <Agustin.Gutierrez@amd.com>,
Pavle Kotarac <Pavle.Kotarac@amd.com>
Subject: Re: How are the DC patches tested?
Date: Tue, 10 May 2022 12:53:51 +0200 [thread overview]
Message-ID: <fb6598f2-322b-5fa7-d4db-8bee38c33c32@molgen.mpg.de> (raw)
In-Reply-To: <DM6PR12MB3529432C69991BA7278574489CC69@DM6PR12MB3529.namprd12.prod.outlook.com>
Dear Daniel,
Am 09.05.22 um 17:21 schrieb Wheeler, Daniel:
> I've made some edits to my cover letter to hopefully make it clearer
> with what is being done.
Thank you.
> Hi all,
>
> This week this patchset was tested on the following systems:
>
> HP Envy 360, with Ryzen 5 4500U
> Lenovo Thinkpad T14s Gen2, with AMD Ryzen 5 5650U
> Sapphire Pulse RX5700XT
> Reference AMD RX6800
> Engineering board with Ryzen 9 5900H
>
> These systems were tested on the following display types:
> eDP, (1080p 60hz [4500U, 5650U, 5900H])
> VGA and DVI (1680x1050 60HZ [DP to VGA/DVI, USB-C to DVI/VGA])
> DP/HDMI/USB-C (1440p 170hz, 4k 60hz, 4k 144hz [Includes USB-C to DP/HDMI adapters])
>
> MST tested with Startech MST14DP123DP and 2x 4k 60Hz displays
> DSC tested with Cable Matters 101075 (DP to 3x DP), and 201375 (USB-C to 3x DP) with 3x 4k60 displays
>
> The testing is a mix of automated and manual tests. Manual testing includes (but is not limited to):
> Changing display configurations and settings
> Benchmark testing
> Feature testing (Freesync, etc.)
>
> Automated testing includes (but is not limited to):
> Script testing (scripts to automate some of the manual checks)
> IGT testing
>
> The patchset consists of the most recent amd-staging-drm-next branch with a selection of patches added on top of it. This goes for both Ubuntu testing and Chrome OS testing.
Please mention the commit hash of the commit at the top of
amd-staging-drm-next.
>
> Tested on Ubuntu 22.04 and Chrome OS
I still do not see the Chrome OS version and devices listed. I think,
that information would be valuable.
>
> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Kind regards,
Paul
prev parent reply other threads:[~2022-05-10 10:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 15:41 [PATCH 00/15] DC Patches May 9, 2022 Stylon Wang
2022-05-06 15:42 ` [PATCH 01/15] drm/amd/display: Refactor LTTPR cap retrieval Stylon Wang
2022-05-06 15:42 ` [PATCH 02/15] drm/amd/display: Reset cached PSR parameters after hibernate Stylon Wang
2022-05-06 15:42 ` [PATCH 03/15] drm/amd/display: move definition of dc_flip_addrs struct Stylon Wang
2022-05-06 15:42 ` [PATCH 04/15] drm/amd/display: do not disable an invalid irq source in hdp finish Stylon Wang
2022-05-06 15:42 ` [PATCH 05/15] drm/amd/display: do not calculate DP2.0 SST payload when link is off Stylon Wang
2022-05-06 15:42 ` [PATCH 06/15] drm/amd/display: do not wait for vblank during pipe programming Stylon Wang
2022-05-06 15:42 ` [PATCH 07/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN in dc Stylon Wang
2022-05-06 15:56 ` Alex Deucher
2022-05-06 17:12 ` Rodrigo Siqueira Jordao
2022-05-06 18:00 ` Alex Deucher
2022-05-07 7:39 ` Cui, Flora
2022-05-09 11:57 ` VURDIGERENATARAJ, CHANDAN
2022-05-09 13:22 ` Rodrigo Siqueira Jordao
2022-05-06 15:42 ` [PATCH 08/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN in dce Stylon Wang
2022-05-06 15:42 ` [PATCH 09/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN in gpio Stylon Wang
2022-05-06 15:42 ` [PATCH 10/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN in irq Stylon Wang
2022-05-06 15:42 ` [PATCH 11/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN for z10 Stylon Wang
2022-05-06 15:42 ` [PATCH 12/15] drm/amd/display: remove redundant CONFIG_DRM_AMD_DC_DCN in amdgpu_dm Stylon Wang
2022-05-06 15:42 ` [PATCH 13/15] drm/amd/display: remove unnecessary else by CONFIG_DRM_AMD_DC_DCN Stylon Wang
2022-05-06 15:42 ` [PATCH 14/15] Revert "drm/amd/display: Fix DCN3 B0 DP Alt Mapping" Stylon Wang
2022-05-06 15:42 ` [PATCH 15/15] drm/amd/display: 3.2.185 Stylon Wang
2022-05-09 13:14 ` [PATCH 00/15] DC Patches May 9, 2022 Wheeler, Daniel
2022-05-09 13:56 ` Paul Menzel
2022-05-09 14:00 ` How are the DC patches tested? (was: [PATCH 00/15] DC Patches May 9, 2022) Paul Menzel
2022-05-09 14:15 ` Rodrigo Siqueira Jordao
2022-05-09 14:28 ` How are the DC patches tested? Paul Menzel
2022-05-09 15:21 ` Wheeler, Daniel
2022-05-10 10:53 ` Paul Menzel [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=fb6598f2-322b-5fa7-d4db-8bee38c33c32@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Agustin.Gutierrez@amd.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Daniel.Wheeler@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Pavle.Kotarac@amd.com \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Roman.Li@amd.com \
--cc=Solomon.Chiu@amd.com \
--cc=Stylon.Wang@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).