Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	intel-gfx@lists.freedesktop.org,
	Andrzej Hajda <andrzej.hajda@intel.com>
Subject: Re: [PATCH] drm/i915: don't make assumptions about intel_wakeref_t type
Date: Fri, 05 Jan 2024 14:59:37 +0200	[thread overview]
Message-ID: <87sf3cx7eu.fsf@intel.com> (raw)
In-Reply-To: <ZZboM17ia5lPn+1o@ideak-desk.fi.intel.com>

On Thu, 04 Jan 2024, Imre Deak <imre.deak@intel.com> wrote:
> On Thu, Jan 04, 2024 at 06:46:00PM +0200, Jani Nikula wrote:
>> intel_wakeref_t is supposed to be a mostly opaque cookie to its
>> users. It should only be checked for being non-zero and set to
>> zero. Debug logging its actual value is meaningless. Switch to just
>> debug logging whether the async_put_wakeref is non-zero.
>> 
>> The issue dates back to much earlier than
>> commit b49e894c3fd8 ("drm/i915: Replace custom intel runtime_pm tracker
>> with ref_tracker library"), but this is the one that brought about a
>> build failure due to the printf format.
>> 
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Closes: https://lore.kernel.org/r/20240102111222.2db11208@canb.auug.org.au
>> Fixes: b49e894c3fd8 ("drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library")
>> Cc: Andrzej Hajda <andrzej.hajda@intel.com>
>> Cc: Imre Deak <imre.deak@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Imre Deak <imre.deak@intel.com>

Thanks for the reviews, pushed to drm-intel-gt-next (because that's
where b49e894c3fd8 was pushed).

BR,
Jani.


>
>> ---
>>  drivers/gpu/drm/i915/display/intel_display_power.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c b/drivers/gpu/drm/i915/display/intel_display_power.c
>> index 5f091502719b..6fd4fa52253a 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_power.c
>> +++ b/drivers/gpu/drm/i915/display/intel_display_power.c
>> @@ -405,8 +405,8 @@ print_async_put_domains_state(struct i915_power_domains *power_domains)
>>  						     struct drm_i915_private,
>>  						     display.power.domains);
>>  
>> -	drm_dbg(&i915->drm, "async_put_wakeref %lu\n",
>> -		power_domains->async_put_wakeref);
>> +	drm_dbg(&i915->drm, "async_put_wakeref: %s\n",
>> +		str_yes_no(power_domains->async_put_wakeref));
>>  
>>  	print_power_domains(power_domains, "async_put_domains[0]",
>>  			    &power_domains->async_put_domains[0]);
>> -- 
>> 2.39.2
>> 

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-01-05 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 16:46 [PATCH] drm/i915: don't make assumptions about intel_wakeref_t type Jani Nikula
2024-01-04 17:17 ` Imre Deak
2024-01-05 12:59   ` Jani Nikula [this message]
2024-01-04 18:32 ` Andrzej Hajda
2024-01-04 21:11 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-01-04 22:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-05  9:47 ` [PATCH] " Andi Shyti

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=87sf3cx7eu.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sfr@canb.auug.org.au \
    /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