From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Richard Gong <richard.gong@amd.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
xinhui.pan@amd.com, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, mario.limonciello@amd.com,
daniel@ffwll.ch, alexander.deucher@amd.com,
christian.koenig@amd.com
Subject: Re: [PATCHv2] drm/amdgpu: disable ASPM on Intel AlderLake based systems
Date: Mon, 11 Apr 2022 09:37:13 +0200 [thread overview]
Message-ID: <76171e7d-43f0-fb7b-6e58-8a09c8f43e88@molgen.mpg.de> (raw)
In-Reply-To: <cacb177f-20e2-b50a-806f-777837fba693@amd.com>
Dear Richard,
Thank you for your response, but please reply to your own reply next time.
Am 11.04.22 um 02:37 schrieb Gong, Richard:
>
> On 4/8/2022 7:19 PM, Paul Menzel wrote:
>> Thank you for your patch.
>>
>> Am 08.04.22 um 21:05 schrieb Richard Gong:
>>> Active State Power Management (ASPM) feature is enabled since kernel
>>> 5.14.
>>> There are some AMD GFX cards (such as WX3200 and RX640) that cannot be
>>> used with Intel AlderLake based systems to enable ASPM. Using these GFX
>>
>> Alder Lake
> Actually there are 2 formats (one with space, another is w/o space) in
> the upstream sources, so I will keep that unchanged and use the format
> w/o space.
Do you mean the Linux kernel sources? Anyway, please use the correct
spelling [1].
Kind regards,
Paul
[1]:
https://ark.intel.com/content/www/us/en/ark/products/codename/147470/products-formerly-alder-lake.html
[2]: https://en.wikipedia.org/wiki/Alder_Lake
next prev parent reply other threads:[~2022-04-11 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 19:05 [PATCHv2] drm/amdgpu: disable ASPM on Intel AlderLake based systems Richard Gong
2022-04-08 19:08 ` Alex Deucher
2022-04-08 19:12 ` Limonciello, Mario
2022-04-09 0:19 ` Paul Menzel
2022-04-11 0:27 ` Gong, Richard
2022-04-11 7:41 ` Paul Menzel
2022-04-11 11:38 ` Gong, Richard
2022-04-11 11:45 ` Paul Menzel
2022-04-11 0:37 ` Gong, Richard
2022-04-11 7:37 ` Paul Menzel [this message]
2022-04-11 4:15 ` Lazar, Lijo
2022-04-11 11:11 ` Gong, Richard
2022-04-11 22:57 ` kernel test robot
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=76171e7d-43f0-fb7b-6e58-8a09c8f43e88@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=richard.gong@amd.com \
--cc=xinhui.pan@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;
as well as URLs for NNTP newsgroup(s).