All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Juan Escamilla <jcescami@wasd.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/gt: Reflect the true and current status of rc6_enable
Date: Mon, 22 Jan 2024 15:39:22 -0500	[thread overview]
Message-ID: <Za7SeuSoXAWghhXS@intel.com> (raw)
In-Reply-To: <20240116172922.3460695-1-jcescami@wasd.net>

On Tue, Jan 16, 2024 at 09:29:19AM -0800, Juan Escamilla wrote:
> The sysfs file is named 'enabled', thus users might want to know the
> true state of the RC6 instead of only the indication if the RC6
> should be enabled.
> 
> Let's use rc6.enable directly instead of rc6.supported.

For a moment I got concerned about this case here:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_128839v2/shard-tglu-4/igt@i915_pm_rc6_residency@rc6-idle@gt0-rcs0.html

but then I noticed it pass the test requirement for RC6:
(i915_pm_rc6_residency:5167) DEBUG: Test requirement passed: __pmu_wait_for_rc6(fd)

Which also anyway is using the residency directly.

Then, I'm also happy with the tests that really uses this like
the accuracy and rc6_disable.

So,

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

> 
> Signed-off-by: Juan Escamilla <jcescami@wasd.net>
> ---
>  drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c b/drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
> index 2d3c4dab6d21..c0b202223940 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c
> @@ -182,7 +182,7 @@ static ssize_t rc6_enable_show(struct kobject *kobj,
>  {
>  	struct intel_gt *gt = intel_gt_sysfs_get_drvdata(kobj, attr->attr.name);
>  
> -	return sysfs_emit(buff, "%x\n", gt->rc6.supported);
> +	return sysfs_emit(buff, "%x\n", gt->rc6.enabled);
>  }
>  
>  static ssize_t rc6_enable_dev_show(struct device *dev,
> @@ -191,7 +191,7 @@ static ssize_t rc6_enable_dev_show(struct device *dev,
>  {
>  	struct intel_gt *gt = intel_gt_sysfs_get_drvdata(&dev->kobj, attr->attr.name);
>  
> -	return sysfs_emit(buff, "%x\n", gt->rc6.supported);
> +	return sysfs_emit(buff, "%x\n", gt->rc6.enabled);
>  }
>  
>  static u32 __rc6_residency_ms_show(struct intel_gt *gt)
> -- 
> 2.43.0
> 

      parent reply	other threads:[~2024-01-22 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 17:29 [PATCH] drm/i915/gt: Reflect the true and current status of rc6_enable Juan Escamilla
2024-01-16 18:25 ` ✗ Fi.CI.BAT: failure for " Patchwork
2024-01-18 22:06 ` ✓ Fi.CI.BAT: success for drm/i915/gt: Reflect the true and current status of rc6_enable (rev2) Patchwork
2024-01-19 10:03 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-22 20:39 ` Rodrigo Vivi [this message]

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=Za7SeuSoXAWghhXS@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jcescami@wasd.net \
    /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.