public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm/i915: skip forcewake actions on forcewake-less uncore
Date: Wed, 19 Jun 2019 15:05:56 -0700	[thread overview]
Message-ID: <aadf2e45-fae4-ebe9-9b08-19a1a4b06312@intel.com> (raw)
In-Reply-To: <dc4f1357-baa0-4e1e-9b3b-adcf6dacc279@intel.com>

<snip>

>>>   }
>>>   void intel_uncore_fini_mmio(struct intel_uncore *uncore)
>>>   {
>>> -    iosf_mbi_punit_acquire();
>>> -    iosf_mbi_unregister_pmic_bus_access_notifier_unlocked(
>>> -        &uncore->pmic_bus_access_nb);
>>> -    intel_uncore_forcewake_reset(uncore);
>>> -    iosf_mbi_punit_release();
>>> +    if (intel_uncore_has_forcewake(uncore)) {
>>
>> To avoid hyphotetical obnoxious diffs in the future, like the one for 
>> intel_uncore_prune_mmio_domains above in this patch, maybe invert this 
>> to early return straight away.
> 

Just realized that I hadn't done that in the first place because there 
is a call to uncore_mmio_cleanup() below that we need to always perform 
and on platforms with forcewake it has to be done after clearing that, 
so can't return early.

Daniele

> will do.
> 
> Daniele
> 
>>
>>> +        iosf_mbi_punit_acquire();
>>> +        iosf_mbi_unregister_pmic_bus_access_notifier_unlocked(
>>> +            &uncore->pmic_bus_access_nb);
>>> +        intel_uncore_forcewake_reset(uncore);
>>> +        iosf_mbi_punit_release();
>>> +    }
>>> +
>>>       uncore_mmio_cleanup(uncore);
>>>   }
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-19 22:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 18:09 [PATCH 0/6] Display uncore prep patches Daniele Ceraolo Spurio
2019-06-17 18:09 ` [PATCH 1/6] drm/i915: use vfuncs for reg_read/write_fw_domains Daniele Ceraolo Spurio
2019-06-18  8:31   ` Tvrtko Ursulin
2019-06-17 18:09 ` [PATCH 2/6] drm/i915: kill uncore_sanitize Daniele Ceraolo Spurio
2019-06-17 18:09 ` [PATCH 3/6] drm/i915: kill uncore_to_i915 Daniele Ceraolo Spurio
2019-06-18  8:34   ` Tvrtko Ursulin
2019-06-17 18:09 ` [PATCH 4/6] drm/i915: skip forcewake actions on forcewake-less uncore Daniele Ceraolo Spurio
2019-06-18  9:00   ` Tvrtko Ursulin
2019-06-18 21:12     ` Daniele Ceraolo Spurio
2019-06-19 22:05       ` Daniele Ceraolo Spurio [this message]
2019-06-18 10:22   ` Chris Wilson
2019-06-18 18:40     ` Daniele Ceraolo Spurio
2019-06-18 18:57       ` Chris Wilson
2019-06-17 18:09 ` [PATCH 5/6] drm/i915: dynamically allocate forcewake domains Daniele Ceraolo Spurio
2019-06-18  9:23   ` Tvrtko Ursulin
2019-06-18 23:06     ` Daniele Ceraolo Spurio
2019-06-18 23:23       ` Chris Wilson
2019-06-18 23:37         ` Daniele Ceraolo Spurio
2019-06-19 14:22       ` Tvrtko Ursulin
2019-06-17 18:09 ` [PATCH 6/6] drm/i915/gvt: decouple check_vgpu() from uncore_init() Daniele Ceraolo Spurio
2019-06-18 10:49   ` Chris Wilson
2019-06-17 18:53 ` ✗ Fi.CI.CHECKPATCH: warning for Display uncore prep patches Patchwork
2019-06-17 19:09 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-18  9:15 ` ✓ Fi.CI.IGT: " 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=aadf2e45-fae4-ebe9-9b08-19a1a4b06312@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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