From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: introduce drm_can_sleep and use in intel/radeon drivers.
Date: Thu, 05 Jan 2012 16:10:31 +0000 [thread overview]
Message-ID: <c55c5d$1j3jct@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120105160051.GE3831@phenom.ffwll.local>
On Thu, 5 Jan 2012 17:00:52 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> If MSLEEP is indeed unused, I think it should just die - we have way too
> much yelling cruft from dri1 yonder lying around that hides important
> details like this. Otherwise
It was used, they just happened to all be redundant or mispellings of
wait-for-vblank. All the remaining sleeps now look to be away from the
atomic paths, and so MSLEEP can die for the time being.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-05 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 9:57 [PATCH] drm: introduce drm_can_sleep and use in intel/radeon drivers Dave Airlie
2012-01-05 10:11 ` Michel Dänzer
2012-01-05 16:00 ` Daniel Vetter
2012-01-05 16:10 ` Chris Wilson [this message]
2012-01-06 10:04 ` Dave Airlie
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='c55c5d$1j3jct@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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.