amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: How are the DC patches tested? (was: [PATCH 00/15] DC Patches May 9,  2022)
Date: Mon, 9 May 2022 16:00:09 +0200	[thread overview]
Message-ID: <f284dad0-9a9e-0edb-54df-db97b58451e9@molgen.mpg.de> (raw)
In-Reply-To: <DM6PR12MB352902B7FE179953EBBD474F9CC69@DM6PR12MB3529.namprd12.prod.outlook.com>

[Sorry for the incomplete first message.]

Dear Daniel,


Am 09.05.22 um 15:14 schrieb Wheeler, Daniel:

[…]

> This week this patchset was tested on the following systems:
> 
> Lenovo Thinkpad T14s Gen2 with AMD Ryzen 5 5650U, with the following
> display types: eDP 1080p 60hz, 4k 60hz  (via USB-C to DP/HDMI), 1440p
> 144hz (via USB-C to DP/HDMI), 1680*1050 60hz (via USB-C to DP and
> then DP to DVI/VGA)
> 
> Sapphire Pulse RX5700XT with the following display types: 4k 60hz
> (via DP/HDMI), 1440p 144hz (via DP/HDMI), 1680*1050 60hz (via DP to
> DVI/VGA)
> 
> Reference AMD RX6800 with the following display types: 4k 60hz  (via
> DP/HDMI and USB-C to DP/HDMI), 1440p 144hz (via USB-C to DP/HDMI and
> USB-C to DP/HDMI), 1680*1050 60hz (via DP to DVI/VGA)
> 
> Included testing using a Startech DP 1.4 MST hub at 2x 4k 60hz and
> DSC via USB-C to DP DSC Hub with 3x 4k 60hz.
> 
> Tested on Ubuntu 22.04 with Kernel Version 5.16, and ChromeOS

I am curious, what this means exactly? You clone the Ubuntu Linux 5.16 
kernel source, and then apply your patches on top? (Do they even apply?)

The same for Chrome OS. Do you use Chrome OS Flex [1] with the systems 
you listed? If not, what Google Chromebooks/-boxes did you test with? 
The Linux kernel version is also tied for a device and Chrome OS 
release. Please mention those too.

Is it documented somewhere, what tests you run exactly?


Kind regards,

Paul


[1]: https://chromeenterprise.google/os/chromeosflex/

  parent reply	other threads:[~2022-05-09 14:00 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   ` Paul Menzel [this message]
2022-05-09 14:15     ` How are the DC patches tested? (was: [PATCH 00/15] DC Patches May 9, 2022) 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

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=f284dad0-9a9e-0edb-54df-db97b58451e9@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).