All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Robert N <crshman@gmail.com>,
	intel-gfx@lists.freedesktop.org,
	Arthur Ranyan <arthur.j.runyan@intel.com>
Subject: Re: [PATCH v2] drm/i915: Increase WM memory latency values on SNB
Date: Thu, 15 May 2014 13:45:52 +0300	[thread overview]
Message-ID: <20140515104552.GR18465@intel.com> (raw)
In-Reply-To: <87wqdnnxdn.fsf@intel.com>

On Thu, May 15, 2014 at 01:34:44PM +0300, Jani Nikula wrote:
> On Thu, 15 May 2014, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Thu, May 15, 2014 at 01:13:21PM +0300, Jani Nikula wrote:
> >> On Thu, 08 May 2014, ville.syrjala@linux.intel.com wrote:
> >> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> > +static void snb_wm_latency_quirk(struct drm_device *dev)
> >> > +{
> >> > +	struct drm_i915_private *dev_priv = dev->dev_private;
> >> > +	bool changed;
> >> > +
> >> > +	/*
> >> > +	 * The BIOS provided WM memory latency values are often
> >> > +	 * inadequate for high resolution displays. Adjust them.
> >> > +	 */
> >> > +	changed = ilk_increase_wm_latency(dev_priv, dev_priv->wm.pri_latency, 12) |
> >> > +		ilk_increase_wm_latency(dev_priv, dev_priv->wm.spr_latency, 12) |
> >> > +		ilk_increase_wm_latency(dev_priv, dev_priv->wm.cur_latency, 12);
> >> 
> >> Nitpick, s/|/||/g for bools.
> >
> > Consider side effects.
> 
> Ugh I'm slow today. Some might claim business as usual. I'll hide
> somewhere.
> 
> Before I head under the rock, may I say bitops on bools are still ugly?

I tend to use them but Paulo was also confused by them somewhere else
in the watermark code, so maybe I should stop using them?

I can rewrite as:
changed |= ilk_increase_wm_latency(dev_priv, dev_priv->wm.pri_latency, 12);
changed |= ilk_increase_wm_latency(dev_priv, dev_priv->wm.spr_latency, 12);
changed |= ilk_increase_wm_latency(dev_priv, dev_priv->wm.cur_latency, 12);

or just 3x
if (ilk_increase_wm_latency(...))
	changed = true;

if that helps.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-05-15 10:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  9:00 [PATCH] drm/i915: Increase WM memory latency values on SNB with high pixel clock Jani Nikula
2014-03-21  9:29 ` Chris Wilson
2014-03-21 10:19 ` Daniel Vetter
2014-03-21 17:28   ` Runyan, Arthur J
2014-03-31 18:29     ` Robert Navarro
2014-04-14  9:16       ` Ville Syrjälä
2014-05-08 12:09   ` [PATCH v2] drm/i915: Increase WM memory latency values on SNB ville.syrjala
2014-05-09 15:23     ` Robert Navarro
2014-05-09 15:38       ` [PATCH v2] drm/i915: Increase WM memory latency values?on SNB Ville Syrjälä
2014-05-09 17:46         ` Robert Navarro
2014-05-09 17:54           ` Ville Syrjälä
2014-05-14  0:55             ` Robert Navarro
2014-05-15 14:18               ` Robert Navarro
2014-05-15 10:13     ` [PATCH v2] drm/i915: Increase WM memory latency values on SNB Jani Nikula
2014-05-15 10:16       ` Chris Wilson
2014-05-15 10:34         ` Jani Nikula
2014-05-15 10:45           ` Ville Syrjälä [this message]
2014-05-15 10:58             ` Jani Nikula

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=20140515104552.GR18465@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=arthur.j.runyan@intel.com \
    --cc=crshman@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.