From: Eric Huang <jinhuieric.huang-5C7GfCeVMHo@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH 1/3] Revert "drm/amd/powerply: fix power reading on Fiji"
Date: Wed, 4 Apr 2018 11:15:28 -0400 [thread overview]
Message-ID: <739a70c9-228f-e910-0128-42503a8b69ac@amd.com> (raw)
In-Reply-To: <1522830304-15505-1-git-send-email-Rex.Zhu-5C7GfCeVMHo@public.gmane.org>
Did you contact tools team about this? Since the smc messages
PPSMC_MSG_PmStatusLogStart and PPSMC_MSG_PmStatusLogSample are
exclusively used by tools, driver just shared it. And AGT gets different
result as driver if you change it back to 20ms. To keep consistent
result as AGT, please verify it through full test cases.
Regards,
Eric
On 2018-04-04 04:25 AM, Rex Zhu wrote:
> we don't have limit of [50ms, 4sec] sampling period.
> only confused the average power and max power.
> so don't need to increase delay time.
>
> This reverts commit 462d8dcc9fec0d89f1ff6a1f93f1d4f670878c71.
>
> Signed-off-by: Rex Zhu <Rex.Zhu@amd.com>
> ---
> drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c b/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
> index aaa9f5b..40f2f87 100644
> --- a/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
> +++ b/drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
> @@ -3368,8 +3368,7 @@ static int smu7_get_gpu_power(struct pp_hwmgr *hwmgr,
> "Failed to start pm status log!",
> return -1);
>
> - /* Sampling period from 50ms to 4sec */
> - msleep_interruptible(200);
> + msleep_interruptible(20);
>
> PP_ASSERT_WITH_CODE(!smum_send_msg_to_smc(hwmgr,
> PPSMC_MSG_PmStatusLogSample),
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-04-04 15:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 8:25 [PATCH 1/3] Revert "drm/amd/powerply: fix power reading on Fiji" Rex Zhu
[not found] ` <1522830304-15505-1-git-send-email-Rex.Zhu-5C7GfCeVMHo@public.gmane.org>
2018-04-04 8:25 ` [PATCH 2/3] drm/amd/pp: Refine get_gpu_power for VI Rex Zhu
[not found] ` <1522830304-15505-2-git-send-email-Rex.Zhu-5C7GfCeVMHo@public.gmane.org>
2018-04-04 15:36 ` Eric Huang
[not found] ` <a3566d2f-4b35-00b4-1df1-ab50076f704c-5C7GfCeVMHo@public.gmane.org>
2018-04-04 15:50 ` Zhu, Rex
[not found] ` <CY4PR12MB1687C34CD0753343A795544CFBA40-rpdhrqHFk06Y0SjTqZDccQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-04-04 16:00 ` Eric Huang
[not found] ` <dfcb5127-c6ad-2a09-793e-42ca3cdcff1d-5C7GfCeVMHo@public.gmane.org>
2018-04-04 16:05 ` Zhu, Rex
2018-04-04 8:25 ` [PATCH 3/3] drm/amd/pp: Remove dead struct pp_gpu_power Rex Zhu
2018-04-04 15:15 ` Eric Huang [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 6:31 [PATCH 1/3] Revert "drm/amd/powerply: fix power reading on Fiji" Rex Zhu
[not found] ` <1523428307-7969-1-git-send-email-Rex.Zhu-5C7GfCeVMHo@public.gmane.org>
2018-04-11 17:19 ` Alex Deucher
[not found] ` <CADnq5_PjDQ1LkTM-=h6k6WJt1Auukq1tAnM77Vz579wxVyP4oQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-04-11 17:33 ` Eric Huang
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=739a70c9-228f-e910-0128-42503a8b69ac@amd.com \
--to=jinhuieric.huang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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