dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 1/5] drm/i915/fbdev: Always forward hotplug events
Date: Thu, 6 Jul 2017 15:05:19 +0200	[thread overview]
Message-ID: <e71fd870-1851-ac2f-b0d2-2b904d0356f9@linux.intel.com> (raw)
In-Reply-To: <20170706130023.28417-1-daniel.vetter@ffwll.ch>

Op 06-07-17 om 15:00 schreef Daniel Vetter:
> With deferred fbdev setup we always need to forward hotplug events,
> even if fbdev isn't fully set up yet. Otherwise the deferred setup
> will neer happen.
>
> Originally this check was added in
>
> commit c45eb4fed12d278d3619f1904885bd0d7bcbf036 (tag: drm-intel-next-fixes-2016-08-05)
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Wed Jul 13 18:34:45 2016 +0100
>
>     drm/i915/fbdev: Check for the framebuffer before use
>
> But the specific case of the hotplug function blowing up was fixed in
>
> commit 50c3dc970a09b3b60422a58934cc27a413288bab
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Fri Jun 27 17:19:22 2014 +0200
>
>     drm/fb-helper: Fix hpd vs. initial config races
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_fbdev.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
> index f11ee039ff45..5536591d3da0 100644
> --- a/drivers/gpu/drm/i915/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/intel_fbdev.c
> @@ -821,7 +821,7 @@ void intel_fbdev_output_poll_changed(struct drm_device *dev)
>  {
>  	struct intel_fbdev *ifbdev = to_i915(dev)->fbdev;
>  
> -	if (ifbdev && ifbdev->vma)
> +	if (ifbdev)
>  		drm_fb_helper_hotplug_event(&ifbdev->helper);
>  }
>  

Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Could you also change the @intel.com to @linux.intel.com in second patch? :-)

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-07-06 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 13:00 [PATCH 1/5] drm/i915/fbdev: Always forward hotplug events Daniel Vetter
2017-07-06 13:00 ` [PATCH 2/5] drm/i915: Protect against deferred fbdev setup Daniel Vetter
2017-07-06 13:00 ` [PATCH 3/5] drm/fb-helper: Support deferred setup Daniel Vetter
2017-07-06 13:00 ` [PATCH 4/5] drm/exynos: Remove custom FB helper " Daniel Vetter
2017-07-06 13:00 ` [PATCH 5/5] drm/hisilicon: " Daniel Vetter
2017-07-07 13:28   ` Sean Paul
2017-07-20 17:59     ` Daniel Vetter
2017-07-06 13:05 ` Maarten Lankhorst [this message]
2017-07-14 13:15   ` [PATCH 1/5] drm/i915/fbdev: Always forward hotplug events Daniel Vetter
2017-07-10 12:15 ` [Intel-gfx] " Jani Nikula
2017-07-10 15:02   ` 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=e71fd870-1851-ac2f-b0d2-2b904d0356f9@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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