All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Quan, Evan" <Evan.Quan@amd.com>
To: "Lazar, Lijo" <Lijo.Lazar@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Chen, Guchun" <Guchun.Chen@amd.com>
Subject: RE: [PATCH] drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable platform
Date: Fri, 24 Dec 2021 12:31:19 +0000	[thread overview]
Message-ID: <DM6PR12MB261951179C3BBBA560B2BA28E47F9@DM6PR12MB2619.namprd12.prod.outlook.com> (raw)
In-Reply-To: <2de02d4d-3c68-d8cd-5685-81b1f29b170e@amd.com>

[AMD Official Use Only]



> -----Original Message-----
> From: Lazar, Lijo <Lijo.Lazar@amd.com>
> Sent: Friday, December 24, 2021 12:44 PM
> To: Quan, Evan <Evan.Quan@amd.com>; amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; Chen, Guchun
> <Guchun.Chen@amd.com>
> Subject: Re: [PATCH] drm/amdgpu: put SMU into proper state on runpm
> suspending for BOCO capable platform
> 
> 
> 
> On 12/24/2021 8:46 AM, Evan Quan wrote:
> > By setting mp1_state as PP_MP1_STATE_UNLOAD, MP1 will do some
> proper
> > cleanups and put itself into a state ready for PNP(which fits the scenario
> BOCO stands for).
> 
> "BOCO similar to PNP" is not correct. Mention this as a workaround. With that
> changed
[Quan, Evan] Sorry for the confusing. I did not mean "BOCO" == "PNP". What I wanted to express is for BOCO/PNP(unlike BACO), SMU does not have to be alive.
From that perspective, it's reasonable to share the SMU cleanup process designed for PNP for BOCO. Anyway thanks for pointing this out. I will drop that confusing expression.

BR
Evan
> 	Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
> 
> Thanks,
> Lijo
> 
> > That can address some random resuming failure observed on BOCO
> capable platforms.
> >
> > Signed-off-by: Evan Quan <evan.quan@amd.com>
> > Change-Id: I9804c4f04b6d2ef737b076cabf85d2880179efe2
> > ---
> >   drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 15 +++++++++++++++
> >   1 file changed, 15 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > index e431c7f10755..ad8370b41e74 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> > @@ -2235,12 +2235,27 @@ static int
> amdgpu_pmops_runtime_suspend(struct device *dev)
> >   	if (amdgpu_device_supports_px(drm_dev))
> >   		drm_dev->switch_power_state =
> DRM_SWITCH_POWER_CHANGING;
> >
> > +	/*
> > +	 * By setting mp1_state as PP_MP1_STATE_UNLOAD, MP1 will do
> some
> > +	 * proper cleanups and put itself into a state ready for PNP. That
> > +	 * can address some random resuming failure observed on BOCO
> capable
> > +	 * platforms.
> > +	 * TODO: this may be also needed for PX capable platform.
> > +	 */
> > +	if (amdgpu_device_supports_boco(drm_dev))
> > +		adev->mp1_state = PP_MP1_STATE_UNLOAD;
> > +
> >   	ret = amdgpu_device_suspend(drm_dev, false);
> >   	if (ret) {
> >   		adev->in_runpm = false;
> > +		if (amdgpu_device_supports_boco(drm_dev))
> > +			adev->mp1_state = PP_MP1_STATE_NONE;
> >   		return ret;
> >   	}
> >
> > +	if (amdgpu_device_supports_boco(drm_dev))
> > +		adev->mp1_state = PP_MP1_STATE_NONE;
> > +
> >   	if (amdgpu_device_supports_px(drm_dev)) {
> >   		/* Only need to handle PCI state in the driver for ATPX
> >   		 * PCI core handles it for _PR3.
> >

      reply	other threads:[~2021-12-24 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  3:16 [PATCH] drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable platform Evan Quan
2021-12-24  4:15 ` Alex Deucher
2021-12-24  4:41 ` Chen, Guchun
2021-12-24  5:26   ` Chen, Guchun
2021-12-24  4:43 ` Lazar, Lijo
2021-12-24 12:31   ` Quan, Evan [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=DM6PR12MB261951179C3BBBA560B2BA28E47F9@DM6PR12MB2619.namprd12.prod.outlook.com \
    --to=evan.quan@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Guchun.Chen@amd.com \
    --cc=Lijo.Lazar@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 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.