From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/xe: Check skip_guc_pc before setting SLPC flag
Date: Thu, 4 Jan 2024 10:26:47 +0530 [thread overview]
Message-ID: <dd42753d-5cda-4e95-a299-0cda55df4184@intel.com> (raw)
In-Reply-To: <20231222210109.533215-1-vinay.belgaumkar@intel.com>
Hi Vinay,
On 23-12-2023 02:31, Vinay Belgaumkar wrote:
> Don't set SLPC GuC feature ctl flag if skip_guc_pc is true.
>
> Fixes: 975e4a3795d4 ("drm/xe: Manually setup C6 when skip_guc_pc is set")
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 811e8b201270..0e112b144ec8 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -62,7 +62,12 @@ static u32 guc_ctl_debug_flags(struct xe_guc *guc)
>
> static u32 guc_ctl_feature_flags(struct xe_guc *guc)
> {
> - return GUC_CTL_ENABLE_SLPC;
> + u32 flags = 0;
> +
> + if (!(guc_to_xe(guc))->info.skip_guc_pc)
Frequency attributes freq_min/freq_max may not work when skip_guc_pc is
set. freq_curr also may not work. I think these freq attributes
shouldn't be exposed for skip_guc_pc case.
Regards,
Badal
> + flags |= GUC_CTL_ENABLE_SLPC;
> +
> + return flags;
> }
>
> static u32 guc_ctl_log_params_flags(struct xe_guc *guc)
next prev parent reply other threads:[~2024-01-04 4:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 21:01 [PATCH] drm/xe: Check skip_guc_pc before setting SLPC flag Vinay Belgaumkar
2023-12-22 23:27 ` Lucas De Marchi
2024-01-03 16:52 ` ✓ CI.Patch_applied: success for drm/xe: Check skip_guc_pc before setting SLPC flag (rev2) Patchwork
2024-01-03 16:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-03 16:53 ` ✓ CI.KUnit: success " Patchwork
2024-01-03 17:01 ` ✓ CI.Build: " Patchwork
2024-01-03 17:01 ` ✓ CI.Hooks: " Patchwork
2024-01-03 17:03 ` ✓ CI.checksparse: " Patchwork
2024-01-03 17:38 ` ✓ CI.BAT: " Patchwork
2024-01-04 4:56 ` Nilawar, Badal [this message]
2024-01-04 6:06 ` [PATCH] drm/xe: Check skip_guc_pc before setting SLPC flag Belgaumkar, Vinay
2024-01-04 6:15 ` Nilawar, Badal
2024-01-05 0:36 ` Belgaumkar, Vinay
2024-01-04 9:34 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-04 9:35 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-04 9:36 ` ✓ CI.KUnit: success " Patchwork
2024-01-04 9:43 ` ✓ CI.Build: " Patchwork
2024-01-04 9:44 ` ✓ CI.Hooks: " Patchwork
2024-01-04 9:45 ` ✓ CI.checksparse: " Patchwork
2024-01-04 10:20 ` ✓ CI.BAT: " Patchwork
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=dd42753d-5cda-4e95-a299-0cda55df4184@intel.com \
--to=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=vinay.belgaumkar@intel.com \
/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