From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/2] drm/i915/icl: Drop spurious register read from icl_dbuf_slices_update
Date: Wed, 14 Nov 2018 12:38:22 +0200 [thread overview]
Message-ID: <877ehggd0h.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20181113140207.GD15029@ideak-desk.fi.intel.com>
Imre Deak <imre.deak@intel.com> writes:
> On Fri, Nov 09, 2018 at 04:09:23PM +0200, Mika Kuoppala wrote:
>> Register DBUF_CTL_S2 is read and it's value is not used. As
>> there is no explanation why we should prime the hardware with
>> read, remove it as spurious.
>>
>> Fixes: aa9664ffe863 ("drm/i915/icl: Enable 2nd DBuf slice only when needed")
>> Cc: Mahesh Kumar <mahesh1.kumar@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> Reviewed-by: Imre Deak <imre.deak@intel.com>
Pushed, thanks for review.
-Mika
>
>> ---
>> drivers/gpu/drm/i915/intel_runtime_pm.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c b/drivers/gpu/drm/i915/intel_runtime_pm.c
>> index f945db6ea420..770de2632530 100644
>> --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
>> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
>> @@ -3236,8 +3236,7 @@ static u8 intel_dbuf_max_slices(struct drm_i915_private *dev_priv)
>> void icl_dbuf_slices_update(struct drm_i915_private *dev_priv,
>> u8 req_slices)
>> {
>> - u8 hw_enabled_slices = dev_priv->wm.skl_hw.ddb.enabled_slices;
>> - u32 val;
>> + const u8 hw_enabled_slices = dev_priv->wm.skl_hw.ddb.enabled_slices;
>> bool ret;
>>
>> if (req_slices > intel_dbuf_max_slices(dev_priv)) {
>> @@ -3248,7 +3247,6 @@ void icl_dbuf_slices_update(struct drm_i915_private *dev_priv,
>> if (req_slices == hw_enabled_slices || req_slices == 0)
>> return;
>>
>> - val = I915_READ(DBUF_CTL_S2);
>> if (req_slices > hw_enabled_slices)
>> ret = intel_dbuf_slice_set(dev_priv, DBUF_CTL_S2, true);
>> else
>> --
>> 2.17.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-11-14 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 14:09 [PATCH 1/2] drm/i915/icl: Drop spurious register read from icl_dbuf_slices_update Mika Kuoppala
2018-11-09 14:09 ` [PATCH 2/2] drm/i915: Request no slices if no active pipes Mika Kuoppala
2018-11-09 14:44 ` Mika Kuoppala
2018-11-14 11:11 ` Imre Deak
2018-11-09 14:24 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/icl: Drop spurious register read from icl_dbuf_slices_update Patchwork
2018-11-09 14:58 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-09 15:32 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/icl: Drop spurious register read from icl_dbuf_slices_update (rev2) Patchwork
2018-11-09 15:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-09 21:34 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-13 14:02 ` [PATCH 1/2] drm/i915/icl: Drop spurious register read from icl_dbuf_slices_update Imre Deak
2018-11-14 10:38 ` Mika Kuoppala [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=877ehggd0h.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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;
as well as URLs for NNTP newsgroup(s).