Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Riana Tauro <riana.tauro@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 1/3] drm/xe: Change the name of frequency sysfs attributes
Date: Fri, 8 Dec 2023 10:45:01 +0530	[thread overview]
Message-ID: <b06a5dc2-3389-4473-8e24-aeea89700268@intel.com> (raw)
In-Reply-To: <ZXKf0yVaESLeQ3eB@intel.com>



On 12/8/2023 10:17 AM, Rodrigo Vivi wrote:
> On Thu, Dec 07, 2023 at 11:04:04AM +0530, Riana Tauro wrote:
>> Hi Rodrigo/Suja
>>
>> These changes are removed again in the second patch.
> 
> What? they are not. The final result is something_freq.

The changes made in the guc_pc in this patch are removed and function 
name changed to be called from the freq sysfs layer in the next patch.


-static ssize_t cur_freq_show(struct device *dev,
-			     struct device_attribute *attr, char *buf)
+/**
+ * xe_guc_pc_get_cur_freq - Get Current requested frequency


The next patch changes the name as well. So it is aligning to devfreq.

> 
> The next patch is based on this.
> 
>> Is this patch required?
> 
> and both are required if we want to be prepared for a
> possible alignment with devfreq.
> 
>>
>> Thanks
>> Riana
>>
>> On 12/6/2023 3:06 AM, Rodrigo Vivi wrote:
>>> From: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>>>
>>> Switching the names of frequency sysfs attrbutes to align with
>>> required devfreq changes. The name changes are as below;
>>>
>>> -freq_act -> act_freq
>>> -freq_cur -> cur_freq
>>> -freq_rpn -> rpn_freq
>>> -freq_rpe -> rpe_freq
>>> -freq_rp0 -> rp0_freq
>>> -freq_min -> min_freq
>>> -freq_max -> max_freq
>>>
>>> Signed-off-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> ---
>>>    drivers/gpu/drm/xe/xe_guc_pc.c | 60 +++++++++++++++++-----------------
>>>    1 file changed, 30 insertions(+), 30 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
>>> index d2605a684b1c..b1876fbea669 100644
>>> --- a/drivers/gpu/drm/xe/xe_guc_pc.c
>>> +++ b/drivers/gpu/drm/xe/xe_guc_pc.c
>>> @@ -60,15 +60,15 @@
>>>     * Xe's GuC PC provides a sysfs API for frequency management:
>>>     *
>>>     * device/gt#/freq_* *read-only* files:
>>> - * - freq_act: The actual resolved frequency decided by PCODE.
>>> - * - freq_cur: The current one requested by GuC PC to the Hardware.
>>> - * - freq_rpn: The Render Performance (RP) N level, which is the minimal one.
>>> - * - freq_rpe: The Render Performance (RP) E level, which is the efficient one.
>>> - * - freq_rp0: The Render Performance (RP) 0 level, which is the maximum one.
>>> + * - act_freq: The actual resolved frequency decided by PCODE.
>>> + * - cur_freq: The current one requested by GuC PC to the Hardware.
>>> + * - rpn_freq: The Render Performance (RP) N level, which is the minimal one.
>>> + * - rpe_freq: The Render Performance (RP) E level, which is the efficient one.
>>> + * - rp0_freq: The Render Performance (RP) 0 level, which is the maximum one.
>>>     *
>>>     * device/gt#/freq_* *read-write* files:
>>> - * - freq_min: GuC PC min request.
>>> - * - freq_max: GuC PC max request.
>>> + * - min_freq: GuC PC min request.
>>> + * - max_freq: GuC PC max request.
>>>     *             If max <= min, then freq_min becomes a fixed frequency request.
>>>     *
>>>     * Render-C States:
>>> @@ -388,7 +388,7 @@ static void pc_update_rp_values(struct xe_guc_pc *pc)
>>>    	pc->rpn_freq = min(pc->rpn_freq, pc->rpe_freq);
>>>    }
>>> -static ssize_t freq_act_show(struct device *dev,
>>> +static ssize_t act_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct kobject *kobj = &dev->kobj;
>>> @@ -413,9 +413,9 @@ static ssize_t freq_act_show(struct device *dev,
>>>    	xe_device_mem_access_put(gt_to_xe(gt));
>>>    	return ret;
>>>    }
>>> -static DEVICE_ATTR_RO(freq_act);
>>> +static DEVICE_ATTR_RO(act_freq);
>>> -static ssize_t freq_cur_show(struct device *dev,
>>> +static ssize_t cur_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct kobject *kobj = &dev->kobj;
>>> @@ -442,18 +442,18 @@ static ssize_t freq_cur_show(struct device *dev,
>>>    	xe_device_mem_access_put(gt_to_xe(gt));
>>>    	return ret;
>>>    }
>>> -static DEVICE_ATTR_RO(freq_cur);
>>> +static DEVICE_ATTR_RO(cur_freq);
>>> -static ssize_t freq_rp0_show(struct device *dev,
>>> +static ssize_t rp0_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>>    	return sysfs_emit(buf, "%d\n", pc->rp0_freq);
>>>    }
>>> -static DEVICE_ATTR_RO(freq_rp0);
>>> +static DEVICE_ATTR_RO(rp0_freq);
>>> -static ssize_t freq_rpe_show(struct device *dev,
>>> +static ssize_t rpe_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>> @@ -465,18 +465,18 @@ static ssize_t freq_rpe_show(struct device *dev,
>>>    	xe_device_mem_access_put(xe);
>>>    	return sysfs_emit(buf, "%d\n", pc->rpe_freq);
>>>    }
>>> -static DEVICE_ATTR_RO(freq_rpe);
>>> +static DEVICE_ATTR_RO(rpe_freq);
>>> -static ssize_t freq_rpn_show(struct device *dev,
>>> +static ssize_t rpn_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>>    	return sysfs_emit(buf, "%d\n", pc->rpn_freq);
>>>    }
>>> -static DEVICE_ATTR_RO(freq_rpn);
>>> +static DEVICE_ATTR_RO(rpn_freq);
>>> -static ssize_t freq_min_show(struct device *dev,
>>> +static ssize_t min_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>> @@ -513,7 +513,7 @@ static ssize_t freq_min_show(struct device *dev,
>>>    	return ret;
>>>    }
>>> -static ssize_t freq_min_store(struct device *dev, struct device_attribute *attr,
>>> +static ssize_t min_freq_store(struct device *dev, struct device_attribute *attr,
>>>    			      const char *buff, size_t count)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>> @@ -543,9 +543,9 @@ static ssize_t freq_min_store(struct device *dev, struct device_attribute *attr,
>>>    	xe_device_mem_access_put(pc_to_xe(pc));
>>>    	return ret ?: count;
>>>    }
>>> -static DEVICE_ATTR_RW(freq_min);
>>> +static DEVICE_ATTR_RW(min_freq);
>>> -static ssize_t freq_max_show(struct device *dev,
>>> +static ssize_t max_freq_show(struct device *dev,
>>>    			     struct device_attribute *attr, char *buf)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>> @@ -571,7 +571,7 @@ static ssize_t freq_max_show(struct device *dev,
>>>    	return ret;
>>>    }
>>> -static ssize_t freq_max_store(struct device *dev, struct device_attribute *attr,
>>> +static ssize_t max_freq_store(struct device *dev, struct device_attribute *attr,
>>>    			      const char *buff, size_t count)
>>>    {
>>>    	struct xe_guc_pc *pc = dev_to_pc(dev);
>>> @@ -601,7 +601,7 @@ static ssize_t freq_max_store(struct device *dev, struct device_attribute *attr,
>>>    	xe_device_mem_access_put(pc_to_xe(pc));
>>>    	return ret ?: count;
>>>    }
>>> -static DEVICE_ATTR_RW(freq_max);
>>> +static DEVICE_ATTR_RW(max_freq);
>>>    /**
>>>     * xe_guc_pc_c_status - get the current GT C state
>>> @@ -667,13 +667,13 @@ u64 xe_guc_pc_mc6_residency(struct xe_guc_pc *pc)
>>>    }
>>>    static const struct attribute *pc_attrs[] = {
>>> -	&dev_attr_freq_act.attr,
>>> -	&dev_attr_freq_cur.attr,
>>> -	&dev_attr_freq_rp0.attr,
>>> -	&dev_attr_freq_rpe.attr,
>>> -	&dev_attr_freq_rpn.attr,
>>> -	&dev_attr_freq_min.attr,
>>> -	&dev_attr_freq_max.attr,
>>> +	&dev_attr_act_freq.attr,
>>> +	&dev_attr_cur_freq.attr,
>>> +	&dev_attr_rp0_freq.attr,
>>> +	&dev_attr_rpe_freq.attr,
>>> +	&dev_attr_rpn_freq.attr,
>>> +	&dev_attr_min_freq.attr,
>>> +	&dev_attr_max_freq.attr,
>>>    	NULL
>>>    };

  reply	other threads:[~2023-12-08  5:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 21:36 [Intel-xe] [PATCH 1/3] drm/xe: Change the name of frequency sysfs attributes Rodrigo Vivi
2023-12-05 21:36 ` [Intel-xe] [PATCH 2/3] drm/xe: Create a xe_gt_freq component for raw management and sysfs Rodrigo Vivi
2023-12-06 23:52   ` Belgaumkar, Vinay
2023-12-07  5:23   ` Riana Tauro
2023-12-05 21:36 ` [Intel-xe] [PATCH 3/3] drm/xe: Add frequency throttle reasons sysfs attributes Rodrigo Vivi
2023-12-07  5:14   ` Riana Tauro
2023-12-07  5:23     ` Sundaresan, Sujaritha
2023-12-07  5:29       ` Riana Tauro
2023-12-06  3:23 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [1/3] drm/xe: Change the name of frequency " Patchwork
2023-12-06  3:23 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-12-06  3:24 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-12-06  3:32 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-12-06  3:32 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-12-06  3:33 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-12-06  4:10 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-12-07  5:34 ` [Intel-xe] [PATCH 1/3] " Riana Tauro
2023-12-08  4:47   ` Rodrigo Vivi
2023-12-08  5:15     ` Riana Tauro [this message]
2023-12-08  5:29       ` Rodrigo Vivi

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=b06a5dc2-3389-4473-8e24-aeea89700268@intel.com \
    --to=riana.tauro@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=sujaritha.sundaresan@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