AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Coffin <mcoffin13@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] drm/amdgpu/navi10: add OD support for restoring default table
Date: Tue, 28 Jan 2020 11:48:54 -0700	[thread overview]
Message-ID: <f63fecc3-fd56-55cb-4bcf-178ead1628d6@gmail.com> (raw)
In-Reply-To: <CADnq5_NUjjtf_kSut0doWRoRUOqi-OrN=M8=3=sf3JoYiCuuwA@mail.gmail.com>



On 1/28/20 10:26 AM, Alex Deucher wrote:
> On Tue, Jan 28, 2020 at 11:44 AM Matt Coffin <mcoffin13@gmail.com> wrote:

> I just copied that vega20 did.  You may be right.  I haven't paged the
> recent SMU interface stuff into my head in a while.  If so, we should
> also fix the vega20_ppt.c code.

The vega20_ppt code was correct, until we implemented the ability for
the user to write to that overdrive table, which will land in 5.5.

Not entirely sure about the canonical way to distribute changes to
someone else's series, but I can take a crack at fixing this.

>>
>> On 1/25/20 11:48 AM, Alex Deucher wrote:
>>> Was missing before.
>>>
>>> Bug: https://gitlab.freedesktop.org/drm/amd/issues/1020
>>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>>> ---
>>>  drivers/gpu/drm/amd/powerplay/navi10_ppt.c | 8 ++++++++
>>>  1 file changed, 8 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/amd/powerplay/navi10_ppt.c b/drivers/gpu/drm/amd/powerplay/navi10_ppt.c
>>> index d2d45181ae23..f60762f9b143 100644
>>> --- a/drivers/gpu/drm/amd/powerplay/navi10_ppt.c
>>> +++ b/drivers/gpu/drm/amd/powerplay/navi10_ppt.c
>>> @@ -2062,6 +2062,14 @@ static int navi10_od_edit_dpm_table(struct smu_context *smu, enum PP_OD_DPM_TABL
>>>               if (ret)
>>>                       return ret;
>>>               od_table->UclkFmax = input[1];
>>> +             break;
>>> +     case PP_OD_RESTORE_DEFAULT_TABLE:
>>> +             ret = smu_update_table(smu, SMU_TABLE_OVERDRIVE, 0, table_context->overdrive_table, false);
>>> +             if (ret) {
>>> +                     pr_err("Failed to export over drive table!\n");
>>> +                     return ret;
>>> +             }
>>> +
>>>               break;
>>>       case PP_OD_COMMIT_DPM_TABLE:
>>>               navi10_dump_od_table(od_table);
>>>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  reply	other threads:[~2020-01-28 18:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 18:48 [PATCH 1/3] drm/amdgpu/navi: fix index for OD MCLK Alex Deucher
2020-01-25 18:48 ` [PATCH 2/3] drm/amdgpu/navi10: add OD_RANGE for navi overclocking Alex Deucher
2020-01-25 18:48 ` [PATCH 3/3] drm/amdgpu/navi10: add OD support for restoring default table Alex Deucher
2020-01-28 16:44   ` Matt Coffin
2020-01-28 17:26     ` Alex Deucher
2020-01-28 18:48       ` Matt Coffin [this message]
2020-01-28 20:06         ` Alex Deucher
2020-01-28 20:10         ` [PATCH] drm/amdgpu/smu_v11_0: Correct behavior of restoring default tables Matt Coffin
2020-01-28 22:26           ` Alex Deucher
2020-01-28 22:37             ` 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=f63fecc3-fd56-55cb-4bcf-178ead1628d6@gmail.com \
    --to=mcoffin13@gmail.com \
    --cc=alexander.deucher@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