public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: rip out intel_dpio_write again
Date: Wed, 2 May 2012 08:44:27 -0700	[thread overview]
Message-ID: <20120502084427.7f0050c2@bwidawsk.net> (raw)
In-Reply-To: <1335949584-10507-1-git-send-email-daniel.vetter@ffwll.ch>

On Wed,  2 May 2012 11:06:23 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:

> Unfortunately it looks like further vlv patches are still stalled due
> to fried hw, and too many people are a bit annoyed about the unused
> function warning.

It is my preference that you never merge code which you know will
produce a warning. I still stand by adding a __used for intermediate
patches.

> 
> So let's just rip it out, we can easily put it back in again.
> 
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>  drivers/gpu/drm/i915/intel_display.c |   22 ----------------------
>  1 file changed, 22 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index e1716be..045f545 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -384,28 +384,6 @@ out_unlock:
>  	return val;
>  }
>  
> -static void intel_dpio_write(struct drm_i915_private *dev_priv, int reg,
> -			     u32 val)
> -{
> -	unsigned long flags;
> -
> -	spin_lock_irqsave(&dev_priv->dpio_lock, flags);
> -	if (wait_for_atomic_us((I915_READ(DPIO_PKT) & DPIO_BUSY) == 0, 100)) {
> -		DRM_ERROR("DPIO idle wait timed out\n");
> -		goto out_unlock;
> -	}
> -
> -	I915_WRITE(DPIO_DATA, val);
> -	I915_WRITE(DPIO_REG, reg);
> -	I915_WRITE(DPIO_PKT, DPIO_RID | DPIO_OP_WRITE | DPIO_PORTID |
> -		   DPIO_BYTE);
> -	if (wait_for_atomic_us((I915_READ(DPIO_PKT) & DPIO_BUSY) == 0, 100))
> -		DRM_ERROR("DPIO write wait timed out\n");
> -
> -out_unlock:
> -	spin_unlock_irqrestore(&dev_priv->dpio_lock, flags);
> -}
> -
>  static void vlv_init_dpio(struct drm_device *dev)
>  {
>  	struct drm_i915_private *dev_priv = dev->dev_private;



-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2012-05-02 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:06 [PATCH] drm/i915: rip out intel_dpio_write again Daniel Vetter
2012-05-02 15:44 ` Ben Widawsky [this message]
2012-05-02 18:55   ` Jesse Barnes
2012-05-02 20:18     ` Ben Widawsky
2012-05-03  0:22       ` Jesse Barnes
2012-05-03  9:10         ` Daniel Vetter

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=20120502084427.7f0050c2@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /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