From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: matthew.d.roper@intel.com, rodrigo.vivi@intel.com
Subject: Re: [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc support
Date: Fri, 19 Jan 2024 13:55:18 +0530 [thread overview]
Message-ID: <4dd696da-90ef-4612-93de-e812d0a8336e@intel.com> (raw)
In-Reply-To: <20240119081852.1858212-1-badal.nilawar@intel.com>
On 19-01-2024 13:48, Badal Nilawar wrote:
> Expose debugfs entry to check if platform support GuC PC (SLPC) feature.
>
> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
> ---
> drivers/gpu/drm/xe/xe_debugfs.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_debugfs.c b/drivers/gpu/drm/xe/xe_debugfs.c
> index c56fd7d59f05..2f474bf0e7c7 100644
> --- a/drivers/gpu/drm/xe/xe_debugfs.c
> +++ b/drivers/gpu/drm/xe/xe_debugfs.c
> @@ -30,6 +30,13 @@ static struct xe_device *node_to_xe(struct drm_info_node *node)
> return to_xe_device(node->minor->dev);
> }
>
> +static int is_gucpc_supported(struct seq_file *m, void *data)
> +{
> + struct xe_device *xe = node_to_xe(m->private);
> +
> + return (int)!xe->info.skip_guc_pc;
Will change this to
return (xe->info.skip_guc_pc ? 0 : 1);
Regards,
Badal
> +}
> +
> static int info(struct seq_file *m, void *data)
> {
> struct xe_device *xe = node_to_xe(m->private);
> @@ -67,6 +74,7 @@ static int info(struct seq_file *m, void *data)
>
> static const struct drm_info_list debugfs_list[] = {
> {"info", info, 0},
> + {"is_gucpc_supported", is_gucpc_supported, 0},
> };
>
> static int forcewake_open(struct inode *inode, struct file *file)
next prev parent reply other threads:[~2024-01-19 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 8:18 [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc support Badal Nilawar
2024-01-19 8:25 ` Nilawar, Badal [this message]
2024-01-19 11:42 ` Jani Nikula
2024-01-19 8:29 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-19 8:29 ` ✓ CI.checkpatch: " Patchwork
2024-01-19 8:30 ` ✓ CI.KUnit: " Patchwork
2024-01-19 8:37 ` ✓ CI.Build: " Patchwork
2024-01-19 8:37 ` ✓ CI.Hooks: " Patchwork
2024-01-19 8:39 ` ✓ CI.checksparse: " Patchwork
2024-01-19 9:03 ` ✓ CI.BAT: " Patchwork
2024-01-19 9:28 ` [PATCH] " Gupta, Anshuman
2024-01-19 9:31 ` Nilawar, Badal
2024-01-19 9:35 ` Gupta, Anshuman
2024-01-19 9:57 ` Riana Tauro
2024-01-19 12:40 ` Nilawar, Badal
2024-01-19 12:22 ` Nilawar, Badal
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=4dd696da-90ef-4612-93de-e812d0a8336e@intel.com \
--to=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@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 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.