Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Riana Tauro <riana.tauro@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
	vinay.belgaumkar@intel.com, badal.nilawar@intel.com
Subject: Re: [PATCH v5 2/2] drm/xe/xe_gt_idle: add debugfs entry for powergating info
Date: Mon, 9 Sep 2024 15:12:03 +0200	[thread overview]
Message-ID: <f9c11e5f-8ee9-4cd9-9b3c-9f95c146021c@intel.com> (raw)
In-Reply-To: <3371ff33-b300-4aa3-bce0-516c36f3e3c9@intel.com>



On 09.09.2024 14:38, Riana Tauro wrote:
> Hi Jani
> 
> On 9/9/2024 5:32 PM, Jani Nikula wrote:
>> On Fri, 06 Sep 2024, Riana Tauro <riana.tauro@intel.com> wrote:
>>> @@ -288,6 +300,7 @@ static const struct drm_info_list debugfs_list[] = {
>>>       {"topology", .show = xe_gt_debugfs_simple_show, .data = topology},
>>>       {"steering", .show = xe_gt_debugfs_simple_show, .data = steering},
>>>       {"ggtt", .show = xe_gt_debugfs_simple_show, .data = ggtt},
>>> +    {"powergate_info", .show = xe_gt_debugfs_simple_show, .data =
>>> powergate_info},
>>>       {"register-save-restore", .show = xe_gt_debugfs_simple_show,
>>> .data = register_save_restore},
>>>       {"workarounds", .show = xe_gt_debugfs_simple_show, .data =
>>> workarounds},
>>>       {"pat", .show = xe_gt_debugfs_simple_show, .data = pat},
>>> diff --git a/drivers/gpu/drm/xe/xe_gt_idle.c
>>> b/drivers/gpu/drm/xe/xe_gt_idle.c
>>> index 3924f9f3d0a5..85a35ed153a3 100644
>>> --- a/drivers/gpu/drm/xe/xe_gt_idle.c
>>> +++ b/drivers/gpu/drm/xe/xe_gt_idle.c
>>> @@ -53,6 +53,11 @@ pc_to_xe(struct xe_guc_pc *pc)
>>>       return gt_to_xe(gt);
>>>   }
>>>   +static inline const char *str_up_down(bool v)
>>> +{
>>> +    return v ? "up" : "down";
>>> +}
>>
>> Please don't add functions with names that are obviously going to have
>> name collisions with core kernel headers. This now conflicts in
>> linux-next [1]. Please rename until we can merge the real str_up_down()
>> from upstream to drm-xe-next.
>>
>> Also, please don't use static inline in .c files. Just let the compiler
>> do its thing.
> This was suggested in a review comment to have a local copy till the
> function lands in the tree
> 
> https://patchwork.freedesktop.org/patch/605708/?series=136477&rev=1

and there was heads-up [2] for potential conflict that was likely missed

[2]
https://lore.kernel.org/intel-xe/7b0a9a05-3a98-4ec7-9c21-f9743602b16a@intel.com/

> 
> Will remove this and use the function once its merged to drm-xe-next.
> 
> Thanks
> Riana
>>
>> BR,
>> Jani.
>>
>>
>> [1] https://lore.kernel.org/r/20240909195939.067c1c13@canb.auug.org.au
>>
>>

  reply	other threads:[~2024-09-09 13:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  7:11 [PATCH v5 0/2] drm/xe/xe_gt_idle: add debugfs entry for powergating info Riana Tauro
2024-09-06  7:02 ` ✓ CI.Patch_applied: success for drm/xe/xe_gt_idle: add debugfs entry for powergating info (rev5) Patchwork
2024-09-06  7:03 ` ✓ CI.checkpatch: " Patchwork
2024-09-06  7:04 ` ✓ CI.KUnit: " Patchwork
2024-09-06  7:11 ` [PATCH v5 1/2] drm/xe/xe_gt_idle: modify powergate enable condition Riana Tauro
2024-09-06  7:11 ` [PATCH v5 2/2] drm/xe/xe_gt_idle: add debugfs entry for powergating info Riana Tauro
2024-09-09 12:02   ` Jani Nikula
2024-09-09 12:38     ` Riana Tauro
2024-09-09 13:12       ` Michal Wajdeczko [this message]
2024-09-10  6:09         ` Riana Tauro
2024-09-10  9:46           ` Jani Nikula
2024-09-10 11:05   ` Ghimiray, Himal Prasad
2024-09-06  7:16 ` ✓ CI.Build: success for drm/xe/xe_gt_idle: add debugfs entry for powergating info (rev5) Patchwork
2024-09-06  7:18 ` ✓ CI.Hooks: " Patchwork
2024-09-06  7:21 ` ✓ CI.checksparse: " Patchwork
2024-09-06  8:03 ` ✓ CI.BAT: " Patchwork
2024-09-08  8:40 ` ✗ CI.FULL: failure " 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=f9c11e5f-8ee9-4cd9-9b3c-9f95c146021c@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=riana.tauro@intel.com \
    --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