public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Egbert Eich <eich@suse.de>, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: add hotplug activation period to hotplug update mask
Date: Wed, 21 Oct 2015 20:28:54 +0200	[thread overview]
Message-ID: <5627D966.6060707@rempel-privat.de> (raw)
In-Reply-To: <1445437363-3030-1-git-send-email-jani.nikula@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2002 bytes --]

Hi,

no more warnings with this patch.
Thank you!


Am 21.10.2015 um 16:22 schrieb Jani Nikula:
> commit 0706f17c307b056ff6f1848320ba82d76945a6ff
> Author: Egbert Eich <eich@suse.de>
> Date:   Wed Sep 23 16:15:27 2015 +0200
> 
>     drm/i915: Avoid race of intel_crt_detect_hotplug() with HPD interrupt, v2
> 
> added a check with WARN to ensure only bits within the mask are
> enabled. Turns out that doesn't hold for G4X, which spits out:
> 
> [    2.641439] ------------[ cut here ]------------
> [    2.641444] WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/i915/i915_irq.c:182 i915_hotplug_interrupt_update_locked+0x45/0x83()
> [    2.641446] WARN_ON(bits & ~mask)
> etc.
> 
> Add CRT_HOTPLUG_ACTIVATION_PERIOD_64 to the mask to fix the warning.
> 
> Reported-by: Oleksij Rempel <linux@rempel-privat.de>
> References: https://bugzilla.kernel.org/show_bug.cgi?id=104991
> Fixes: 0706f17c307b ("drm/i915: Avoid race of intel_crt_detect_hotplug() with HPD interrupt, v2")
> Cc: Egbert Eich <eich@suse.de>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
>  drivers/gpu/drm/i915/i915_irq.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
> index 7f91f74961f4..5b9f63d4318b 100644
> --- a/drivers/gpu/drm/i915/i915_irq.c
> +++ b/drivers/gpu/drm/i915/i915_irq.c
> @@ -4236,9 +4236,10 @@ static void i915_hpd_irq_setup(struct drm_device *dev)
>  
>  	/* Ignore TV since it's buggy */
>  	i915_hotplug_interrupt_update_locked(dev_priv,
> -				      (HOTPLUG_INT_EN_MASK
> -				       | CRT_HOTPLUG_VOLTAGE_COMPARE_MASK),
> -				      hotplug_en);
> +					     HOTPLUG_INT_EN_MASK |
> +					     CRT_HOTPLUG_VOLTAGE_COMPARE_MASK |
> +					     CRT_HOTPLUG_ACTIVATION_PERIOD_64,
> +					     hotplug_en);
>  }
>  
>  static irqreturn_t i965_irq_handler(int irq, void *arg)
> 


-- 
Regards,
Oleksij


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2015-10-21 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 14:22 [PATCH] drm/i915: add hotplug activation period to hotplug update mask Jani Nikula
2015-10-21 14:32 ` Ville Syrjälä
2015-10-22  7:46   ` Jani Nikula
2015-10-22  8:03     ` Daniel Vetter
2015-10-22 11:27       ` Jani Nikula
2015-10-22 12:01     ` Ville Syrjälä
2015-10-22 12:43       ` Jani Nikula
2015-10-21 18:28 ` Oleksij Rempel [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=5627D966.6060707@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eich@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox