From: "Quan, Evan" <Evan.Quan@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: RE: [PATCH] drm/amd/powerplay: avoid DPM reenable process on Navi1x ASICs
Date: Tue, 12 Nov 2019 01:33:44 +0000 [thread overview]
Message-ID: <MN2PR12MB3344DA38E540DD655ECC75ADE4770@MN2PR12MB3344.namprd12.prod.outlook.com> (raw)
Message-ID: <20191112013344.YMo4LGHL6GWk7IUZ3tM93ZdWjxUkudA8V-rn5lVN1bs@z> (raw)
In-Reply-To: <CADnq5_OhXnzYx6EgMM87dh1jgUi6Br86Axwi_KfvLjXuO2+gxw@mail.gmail.com>
> -----Original Message-----
> From: Alex Deucher <alexdeucher@gmail.com>
> Sent: Tuesday, November 12, 2019 1:34 AM
> To: Quan, Evan <Evan.Quan@amd.com>
> Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
> Subject: Re: [PATCH] drm/amd/powerplay: avoid DPM reenable process on
> Navi1x ASICs
>
> On Mon, Nov 11, 2019 at 4:25 AM Evan Quan <evan.quan@amd.com> wrote:
> >
> > Otherwise, without RLC reinitialization, the DPM reenablement will
> > fail. That affects the custom pptable uploading.
> >
> > Change-Id: I6fe2ed5ce23f2a5b66f371c0b6d1f924837e5af6
> > Signed-off-by: Evan Quan <evan.quan@amd.com>
> > ---
> > drivers/gpu/drm/amd/powerplay/amdgpu_smu.c | 32 +++++++++++++++--
> --
> > .../gpu/drm/amd/powerplay/inc/amdgpu_smu.h | 1 +
> > 2 files changed, 26 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/amd/powerplay/amdgpu_smu.c
> > b/drivers/gpu/drm/amd/powerplay/amdgpu_smu.c
> > index 76a4154b3be2..a4d67b30fd72 100644
> > --- a/drivers/gpu/drm/amd/powerplay/amdgpu_smu.c
> > +++ b/drivers/gpu/drm/amd/powerplay/amdgpu_smu.c
> > @@ -1293,10 +1293,25 @@ static int smu_hw_fini(void *handle)
> > return ret;
> > }
> >
> > - ret = smu_stop_dpms(smu);
> > - if (ret) {
> > - pr_warn("Fail to stop Dpms!\n");
> > - return ret;
> > + /*
> > + * For custom pptable uploading, skip the DPM features
> > + * disable process on Navi1x ASICs.
> > + * - As the gfx related features are under control of
> > + * RLC on those ASICs. RLC reinitialization will be
> > + * needed to reenable them. That will cost much more
> > + * efforts.
> > + *
> > + * - SMU firmware can handle the DPM reenablement
> > + * properly.
> > + */
> > + if (!smu->uploading_custom_pp_table ||
> > + !((adev->asic_type >= CHIP_NAVI10) &&
> > + (adev->asic_type <= CHIP_NAVI12))) {
> > + ret = smu_stop_dpms(smu);
> > + if (ret) {
> > + pr_warn("Fail to stop Dpms!\n");
> > + return ret;
> > + }
> > }
> >
> > kfree(table_context->driver_pptable);
> > @@ -1324,13 +1339,16 @@ int smu_reset(struct smu_context *smu)
> > struct amdgpu_device *adev = smu->adev;
> > int ret = 0;
> >
> > + smu->uploading_custom_pp_table = true;
> > +
>
> Do we need to differentiate between reloading for a pptable update and
> reloading for a gpu reset or suspend/resume or is that already handled?
[Quan, Evan] That was considered(and as I verified suspend/resume was fine). For gpu reset or suspend/resume, the rlc/gfx will be reinitialized.
So, under those cases, it's OK to perform the dpms disablement.
> Shouldn't we be setting/clearing uploading_custom_pp_table in
> smu_sys_set_pp_table() around the call to smu_reset()?
[Quan, Evan] That's a good point. Will update this in V2.
>
> Alex
>
> > ret = smu_hw_fini(adev);
> > if (ret)
> > - return ret;
> > + goto out;
> >
> > ret = smu_hw_init(adev);
> > - if (ret)
> > - return ret;
> > +
> > +out:
> > + smu->uploading_custom_pp_table = false;
> >
> > return ret;
> > }
> > diff --git a/drivers/gpu/drm/amd/powerplay/inc/amdgpu_smu.h
> > b/drivers/gpu/drm/amd/powerplay/inc/amdgpu_smu.h
> > index 8120e7587585..215841f5fb93 100644
> > --- a/drivers/gpu/drm/amd/powerplay/inc/amdgpu_smu.h
> > +++ b/drivers/gpu/drm/amd/powerplay/inc/amdgpu_smu.h
> > @@ -391,6 +391,7 @@ struct smu_context
> >
> > uint32_t smc_if_version;
> >
> > + bool uploading_custom_pp_table;
> > };
> >
> > struct i2c_adapter;
> > --
> > 2.24.0
> >
> > _______________________________________________
> > amd-gfx mailing list
> > amd-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-11-12 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 9:25 [PATCH] drm/amd/powerplay: avoid DPM reenable process on Navi1x ASICs Evan Quan
2019-11-11 9:25 ` Evan Quan
[not found] ` <20191111092506.18913-1-evan.quan-5C7GfCeVMHo@public.gmane.org>
2019-11-11 17:33 ` Alex Deucher
2019-11-11 17:33 ` Alex Deucher
[not found] ` <CADnq5_OhXnzYx6EgMM87dh1jgUi6Br86Axwi_KfvLjXuO2+gxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-11-12 1:33 ` Quan, Evan [this message]
2019-11-12 1:33 ` Quan, Evan
2019-11-11 23:35 ` Matt Coffin
2019-11-11 23:35 ` Matt Coffin
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=MN2PR12MB3344DA38E540DD655ECC75ADE4770@MN2PR12MB3344.namprd12.prod.outlook.com \
--to=evan.quan@amd.com \
--cc=alexdeucher@gmail.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).