All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, superm1@kernel.org,
	Mario Limonciello <mario.limonciello@amd.com>,
	Lijo Lazar <Lijo.Lazar@amd.com>
Subject: Re: [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume()
Date: Tue, 8 Sep 2026 17:32:49 +0200	[thread overview]
Message-ID: <2026090831-oxygen-ecologist-a7df@gregkh> (raw)
In-Reply-To: <20260908135407.1640233-1-alexander.deucher@amd.com>

On Tue, Sep 08, 2026 at 09:54:07AM -0400, Alex Deucher wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
> 
> User requested power limits and clock settings are already restored as
> part of smu_restore_dpm_user_profile(). It's unnecessary to call the
> same restore as part of smu_resume().
> 
> Revert the following commits to drop that extra restore:
> commit ed4efe426a49 ("drm/amd: Restore cached power limit during resume")
> commit 796ff8a7e01b ("drm/amd: Restore cached manual clock settings during resume")
> commit f9b80514a722 ("drm/amd: Only restore cached manual clock settings in restore if OD enabled")
> 
> Suggested-by: Lijo Lazar <Lijo.Lazar@amd.com>
> Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> (cherry picked from commit 4b6ec94fdae2407d9b8e69e3ec5f879e72ad667e)

What stable tree(s) is this backport for?

thanks,

greg k-h

      reply	other threads:[~2026-09-08 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 13:54 [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() Alex Deucher
2026-09-08 15:32 ` Greg KH [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=2026090831-oxygen-ecologist-a7df@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Lijo.Lazar@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=mario.limonciello@amd.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=superm1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.