From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
Eric Yang <Eric.Yang2@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
richard.gong@amd.com
Subject: Re: [PATCH 1/2] drm/amd/display: Add pstate verification and recovery for DCN31
Date: Thu, 14 Apr 2022 12:45:36 +0200 [thread overview]
Message-ID: <Ylf7UEKnjHW6p7Em@kroah.com> (raw)
In-Reply-To: <20220413153339.1436168-1-alexander.deucher@amd.com>
On Wed, Apr 13, 2022 at 11:33:38AM -0400, Alex Deucher wrote:
> From: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
>
> [Why]
> To debug when p-state is being blocked and avoid PMFW hangs when
> it does occur.
>
> [How]
> Re-use the DCN10 hardware sequencer by adding a new interface for
> verifying p-state high on the hubbub. The interface is mostly the
> same as the DCN10 interface, but the bit definitions have changed for
> the debug bus.
>
> Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Reviewed-by: Eric Yang <Eric.Yang2@amd.com>
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> (cherry picked from commit e7031d8258f1b4d6d50e5e5b5d92ba16f66eb8b4)
> Cc: richard.gong@amd.com
> Cc: nicholas.kazlauskas@amd.com
> Cc: stable@vger.kernel.org # 3.15.x
This does not apply to all of those kernels. Please provide backports
for the ones you want it applied to older than 5.15.y
thanks,
greg k-h
next prev parent reply other threads:[~2022-04-14 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 15:33 [PATCH 1/2] drm/amd/display: Add pstate verification and recovery for DCN31 Alex Deucher
2022-04-13 15:33 ` [PATCH 2/2] drm/amd/display: Fix p-state allow debug index on dcn31 Alex Deucher
2022-04-14 10:45 ` Greg KH [this message]
2022-04-14 13:40 ` [PATCH 1/2] drm/amd/display: Add pstate verification and recovery for DCN31 Deucher, Alexander
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=Ylf7UEKnjHW6p7Em@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Eric.Yang2@amd.com \
--cc=alexander.deucher@amd.com \
--cc=harry.wentland@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=richard.gong@amd.com \
--cc=stable@vger.kernel.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