From: Jani Nikula <jani.nikula@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
LKML <linux-kernel@vger.kernel.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] drm/i915: Fixup legacy plane->crtc link for initial fb config
Date: Thu, 26 Mar 2015 14:08:28 +0200 [thread overview]
Message-ID: <874mp8rmf7.fsf@intel.com> (raw)
In-Reply-To: <1427304638-7897-1-git-send-email-daniel.vetter@ffwll.ch>
On Wed, 25 Mar 2015, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> This is a very similar bug in the load detect code fixed in
>
> commit 9128b040eb774e04bc23777b005ace2b66ab2a85
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Tue Mar 3 17:31:21 2015 +0100
>
> drm/i915: Fix modeset state confusion in the load detect code
>
> But this time around it was the initial fb code that forgot to update
> the plane->crtc pointer. Otherwise it's the exact same bug, with the
> exact same restrains (any set_config call/ioctl that doesn't disable
> the pipe papers over the bug for free, so fairly hard to hit in normal
> testing). So if you want the full explanation just go read that one
> over there - it's rather long ...
>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Josh Boyer <jwboyer@fedoraproject.org>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> This is the version for -next. The one for -fixes just needs an
> s/primary/intel_crtc->base.primary/ and some fudge in the diff. I just
> want to apply this in both trees since with all the cherry-picking the
> conflicts are fun already and with this patch in both places we can
> just go with the code in -next.
I've also picked this up from -next to drm-intel-fixes.
BR,
Jani.
>
> Cheers, Daniel
> ---
> drivers/gpu/drm/i915/intel_display.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index ceb2e61b4c91..cb508542c6ab 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2594,6 +2594,7 @@ intel_find_plane_obj(struct intel_crtc *intel_crtc,
>
> primary->fb = &plane_config->fb->base;
> primary->state->crtc = &intel_crtc->base;
> + primary->crtc = &intel_crtc->base;
> update_state_fb(primary);
>
> return;
> @@ -2627,6 +2628,7 @@ intel_find_plane_obj(struct intel_crtc *intel_crtc,
> drm_framebuffer_reference(c->primary->fb);
> primary->fb = c->primary->fb;
> primary->state->crtc = &intel_crtc->base;
> + primary->crtc = &intel_crtc->base;
> update_state_fb(intel_crtc->base.primary);
> obj->frontbuffer_bits |= INTEL_FRONTBUFFER_PRIMARY(intel_crtc->pipe);
> break;
> --
> 2.1.4
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Matt Roper <matthew.d.roper@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Josh Boyer <jwboyer@fedoraproject.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] drm/i915: Fixup legacy plane->crtc link for initial fb config
Date: Thu, 26 Mar 2015 14:08:28 +0200 [thread overview]
Message-ID: <874mp8rmf7.fsf@intel.com> (raw)
In-Reply-To: <1427304638-7897-1-git-send-email-daniel.vetter@ffwll.ch>
On Wed, 25 Mar 2015, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> This is a very similar bug in the load detect code fixed in
>
> commit 9128b040eb774e04bc23777b005ace2b66ab2a85
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Tue Mar 3 17:31:21 2015 +0100
>
> drm/i915: Fix modeset state confusion in the load detect code
>
> But this time around it was the initial fb code that forgot to update
> the plane->crtc pointer. Otherwise it's the exact same bug, with the
> exact same restrains (any set_config call/ioctl that doesn't disable
> the pipe papers over the bug for free, so fairly hard to hit in normal
> testing). So if you want the full explanation just go read that one
> over there - it's rather long ...
>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Josh Boyer <jwboyer@fedoraproject.org>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> This is the version for -next. The one for -fixes just needs an
> s/primary/intel_crtc->base.primary/ and some fudge in the diff. I just
> want to apply this in both trees since with all the cherry-picking the
> conflicts are fun already and with this patch in both places we can
> just go with the code in -next.
I've also picked this up from -next to drm-intel-fixes.
BR,
Jani.
>
> Cheers, Daniel
> ---
> drivers/gpu/drm/i915/intel_display.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index ceb2e61b4c91..cb508542c6ab 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2594,6 +2594,7 @@ intel_find_plane_obj(struct intel_crtc *intel_crtc,
>
> primary->fb = &plane_config->fb->base;
> primary->state->crtc = &intel_crtc->base;
> + primary->crtc = &intel_crtc->base;
> update_state_fb(primary);
>
> return;
> @@ -2627,6 +2628,7 @@ intel_find_plane_obj(struct intel_crtc *intel_crtc,
> drm_framebuffer_reference(c->primary->fb);
> primary->fb = c->primary->fb;
> primary->state->crtc = &intel_crtc->base;
> + primary->crtc = &intel_crtc->base;
> update_state_fb(intel_crtc->base.primary);
> obj->frontbuffer_bits |= INTEL_FRONTBUFFER_PRIMARY(intel_crtc->pipe);
> break;
> --
> 2.1.4
>
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-26 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 17:30 [PATCH] drm/i915: Fixup legacy plane->crtc link for initial fb config Daniel Vetter
2015-03-25 17:30 ` Daniel Vetter
2015-03-26 9:53 ` shuang.he
2015-03-26 10:24 ` Daniel Vetter
2015-03-26 11:08 ` He, Shuang
2015-03-26 13:12 ` Daniel Vetter
2015-03-26 13:32 ` He, Shuang
2015-03-26 12:08 ` Jani Nikula [this message]
2015-03-26 12:08 ` 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=874mp8rmf7.fsf@intel.com \
--to=jani.nikula@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=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.