&dev->mode_config.plane_list,
>>>>>head) {
>>>>> plane->funcs->destroy(plane);
>>>>> }
>>>>> + list_for_each_entry_safe(crtc, ct, &dev->
On 09/20/2012 02:38 PM, Rob Clark wrote:
> On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim
> wrote:
>> On 09/17/2012 06:38 PM, Chris Wilson wrote:
>>> As during the plane cleanup, we wish to disable the hardware and
>>> so may modify state on the associated CRTC, that CRTC must continue to
>>> ex
On 09/17/2012 06:38 PM, Chris Wilson wrote:
> As during the plane cleanup, we wish to disable the hardware and
> so may modify state on the associated CRTC, that CRTC must continue to
> exist until we are finished.
A similar issue can occur in the drm_framebuffer_cleanup(). If crtc and
plane use s
}
> >>> + list_for_each_entry_safe(crtc, ct, &dev->mode_config.crtc_list,
> >>> head) {
> >>> + crtc->funcs->destroy(crtc);
> >>> + }
> >>> +
> >>> idr_remove_all(&d
_
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
From: Chris Wilson
Subject: Re: [PATCH] drm: Destroy the planes prior to destroying the associated
CRTC
To: Rob Clark , Joonyoung Shim
Cc: airl...@redhat.com, sta...@vger.kernel.org, dri-devel
> >>>+ list_for_each_entry_safe(crtc, ct, &dev->mode_config.crtc_list,
> >>> head) {
> >>> + crtc->funcs->destroy(crtc);
> >>> + }
> >>> +
> >>> idr_remove_all(&dev->mod
On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim
wrote:
> On 09/17/2012 06:38 PM, Chris Wilson wrote:
>>
>> As during the plane cleanup, we wish to disable the hardware and
>> so may modify state on the associated CRTC, that CRTC must continue to
>> exist until we are finished.
>
>
> A similar iss
On 09/20/2012 02:38 PM, Rob Clark wrote:
On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim wrote:
On 09/17/2012 06:38 PM, Chris Wilson wrote:
As during the plane cleanup, we wish to disable the hardware and
so may modify state on the associated CRTC, that CRTC must continue to
exist until we are
On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim wrote:
> On 09/17/2012 06:38 PM, Chris Wilson wrote:
>>
>> As during the plane cleanup, we wish to disable the hardware and
>> so may modify state on the associated CRTC, that CRTC must continue to
>> exist until we are finished.
>
>
> A similar issu
On 09/17/2012 06:38 PM, Chris Wilson wrote:
As during the plane cleanup, we wish to disable the hardware and
so may modify state on the associated CRTC, that CRTC must continue to
exist until we are finished.
A similar issue can occur in the drm_framebuffer_cleanup(). If crtc and
plane use same
Am Mittwoch, den 19.09.2012, 11:34 +0200 schrieb Daniel Vetter:
> On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> > On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes > virtuousgeek.org> wrote:
> > > Yeah, looks good. Did we used to not touch the crtc in the plane
> > > cleanup? Ei
On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes virtuousgeek.org> wrote:
> > Yeah, looks good. Did we used to not touch the crtc in the plane
> > cleanup? Either way this is safer.
>
> I think the bug only came to light because QA
On Wed, 19 Sep 2012 11:45:34 +0200, Paul Menzel wrote:
> Am Mittwoch, den 19.09.2012, 11:34 +0200 schrieb Daniel Vetter:
> > On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> > > On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes > > virtuousgeek.org> wrote:
> > > > Yeah, looks good.
On Wed, 19 Sep 2012 11:45:34 +0200, Paul Menzel
wrote:
> Am Mittwoch, den 19.09.2012, 11:34 +0200 schrieb Daniel Vetter:
> > On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> > > On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes
> > > wrote:
> > > > Yeah, looks good. Did we used t
Am Mittwoch, den 19.09.2012, 11:34 +0200 schrieb Daniel Vetter:
> On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> > On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes
> > wrote:
> > > Yeah, looks good. Did we used to not touch the crtc in the plane
> > > cleanup? Either way this i
On Mon, Sep 17, 2012 at 04:04:23PM +0100, Chris Wilson wrote:
> On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes
> wrote:
> > Yeah, looks good. Did we used to not touch the crtc in the plane
> > cleanup? Either way this is safer.
>
> I think the bug only came to light because QA is now routine
On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes
wrote:
> Yeah, looks good. Did we used to not touch the crtc in the plane
> cleanup? Either way this is safer.
I think the bug only came to light because QA is now routinely running
with slub_debug.
-Chris
--
Chris Wilson, Intel Open Source Te
As during the plane cleanup, we wish to disable the hardware and
so may modify state on the associated CRTC, that CRTC must continue to
exist until we are finished.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
Signed-off-by: Chris Wilson
Cc: Jesse Barnes
Cc: stable at vger.kernel
On Mon, 17 Sep 2012 07:55:59 -0700, Jesse Barnes
wrote:
> Yeah, looks good. Did we used to not touch the crtc in the plane
> cleanup? Either way this is safer.
I think the bug only came to light because QA is now routinely running
with slub_debug.
-Chris
--
Chris Wilson, Intel Open Source Te
On Mon, 17 Sep 2012 10:38:03 +0100
Chris Wilson wrote:
> As during the plane cleanup, we wish to disable the hardware and
> so may modify state on the associated CRTC, that CRTC must continue to
> exist until we are finished.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
> Sig
On Mon, 17 Sep 2012 10:38:03 +0100
Chris Wilson wrote:
> As during the plane cleanup, we wish to disable the hardware and
> so may modify state on the associated CRTC, that CRTC must continue to
> exist until we are finished.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
> Sig
As during the plane cleanup, we wish to disable the hardware and
so may modify state on the associated CRTC, that CRTC must continue to
exist until we are finished.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
Signed-off-by: Chris Wilson
Cc: Jesse Barnes
Cc: sta...@vger.kernel.or
22 matches
Mail list logo
