dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Rob Clark <rob.clark@linaro.org>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm: Destroy the planes prior to destroying the associated CRTC
Date: Thu, 20 Sep 2012 15:10:39 +0900	[thread overview]
Message-ID: <505AB35F.90608@samsung.com> (raw)
In-Reply-To: <CAF6AEGvOZa_ZhRJN212Rsn-gMMUyWoLT6UFY9iindi8AWx9GvA@mail.gmail.com>

On 09/20/2012 02:38 PM, Rob Clark wrote:
> On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim <jy0922.shim@samsung.com> 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 issue can occur in the drm_framebuffer_cleanup(). If crtc and
>> plane use same framebuffer and the framebuffer is destroyed, crtc is
>> turned off prior to turning off plane.
>>
> I imagine my patch to add refcnt'ing to fb would help in this case..
>
> BR,
> -R

Even if the patch to add refcnt'ing to fb is applied, same issue will
occur in the drm_framebuffer_remove(). It can delay to destroy the fb,
but cannot change crtc and plane disable order.

>>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54101
>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
>>> Cc: stable@vger.kernel.org
>>> ---
>>>    drivers/gpu/drm/drm_crtc.c |    8 ++++----
>>>    1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
>>> index 6fbfc24..af81f77 100644
>>> --- a/drivers/gpu/drm/drm_crtc.c
>>> +++ b/drivers/gpu/drm/drm_crtc.c
>>> @@ -1034,15 +1034,15 @@ void drm_mode_config_cleanup(struct drm_device
>>> *dev)
>>>                  fb->funcs->destroy(fb);
>>>          }
>>>    -     list_for_each_entry_safe(crtc, ct, &dev->mode_config.crtc_list,
>>> head) {
>>> -               crtc->funcs->destroy(crtc);
>>> -       }
>>> -
>>>          list_for_each_entry_safe(plane, plt, &dev->mode_config.plane_list,
>>>                                   head) {
>>>                  plane->funcs->destroy(plane);
>>>          }
>>>    +     list_for_each_entry_safe(crtc, ct, &dev->mode_config.crtc_list,
>>> head) {
>>> +               crtc->funcs->destroy(crtc);
>>> +       }
>>> +
>>>          idr_remove_all(&dev->mode_config.crtc_idr);
>>>          idr_destroy(&dev->mode_config.crtc_idr);
>>>    }
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2012-09-20  6:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17  9:38 [PATCH] drm: Destroy the planes prior to destroying the associated CRTC Chris Wilson
2012-09-17 14:55 ` Jesse Barnes
2012-09-17 15:04   ` Chris Wilson
2012-09-19  9:34     ` Daniel Vetter
2012-09-19  9:45       ` Paul Menzel
2012-09-19 10:26         ` Chris Wilson
2012-09-20  2:52 ` Joonyoung Shim
2012-09-20  5:38   ` Rob Clark
2012-09-20  6:10     ` Joonyoung Shim [this message]
2012-09-20  7:49       ` Chris Wilson
2012-09-20  8:08         ` Joonyoung Shim

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=505AB35F.90608@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=rob.clark@linaro.org \
    --cc=stable@vger.kernel.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