From: Imre Deak <imre.deak@intel.com>
To: Inki Dae <inki.dae@samsung.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rob Clark <rob.clark@linaro.org>
Subject: Re: [PATCH v2 0/4] drm/exynos,intel: fix locking for flip/vbl event list
Date: Wed, 07 Nov 2012 12:43:19 +0200 [thread overview]
Message-ID: <1352284999.20257.10.camel@ideak-mobl> (raw)
In-Reply-To: <CAAQKjZOhhF92gc0Y_sedP_vwTvQMC=r5SGYX-Z3E7yULx+DpTQ@mail.gmail.com>
On Wed, 2012-11-07 at 18:31 +0900, Inki Dae wrote:
> 2012/11/2 Imre Deak <imre.deak@intel.com>
> The patchset adds the missing event_lock when accessing the
> vblank_event_list in drm_vblank_off() and as preparation for
> this
> also fixes a few other issues in the exynos driver.
> This is also a dependency for Rob Clark's
> drm_send_vblank_event()
> rework as that would trigger a warning for the unhold
> event_lock without
> this changeset.
> The exynos changes are only compile tested, the rest is tested
> on an
> Intel IVB machine on top of drm-intel-nightly +
> drm_send_vblank_event()
> rework, with i-g-t/flip_test.
> Hi Imre,
> Works fine. But we should wait for Rob's patch set to be merged to
> -next, and this may be rebased on top of latest Rob's patch set again.
Ok, thanks for checking this. I assume then that this patchset will get
merged through your tree.
I think Rob's patchset depends on this, so ideally this should go first.
Otherwise the i915 driver would trigger the WARN in his patchset due to
the unheld event_lock.
--Imre
next prev parent reply other threads:[~2012-11-07 10:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 22:03 [PATCH 1/2] drm: fix order of event_lock wrt. vblank_time_clock Imre Deak
2012-10-31 22:03 ` [PATCH 2/2] drm/i915: lock event_lock for drm_vblank_off() Imre Deak
2012-10-31 22:46 ` Daniel Vetter
2012-11-01 9:34 ` Imre Deak
2012-11-01 9:22 ` [PATCH 1/2] drm: fix order of event_lock wrt. vblank_time_clock Imre Deak
2012-11-02 11:30 ` [PATCH v2 0/4] drm/exynos, intel: fix locking for flip/vbl event list Imre Deak
2012-11-07 9:31 ` Inki Dae
2012-11-07 10:43 ` Imre Deak [this message]
2012-11-07 16:25 ` Inki Dae
2012-11-07 16:28 ` Rob Clark
2012-11-07 16:42 ` Inki Dae
2012-11-02 11:30 ` [PATCH v2 1/4] drm/exynos: hold event_lock while accessing pageflip_event_list Imre Deak
2012-11-02 11:30 ` [PATCH v2 2/4] drm/exynos: call drm_vblank_put for each queued flip event Imre Deak
2012-11-02 11:30 ` [PATCH v2 3/4] drm/exynos: fix lockdep for event_lock wrt. vbl_time_lock Imre Deak
2012-11-02 11:30 ` [PATCH v2 4/4] drm: hold event_lock while accessing vblank_event_list Imre Deak
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=1352284999.20257.10.camel@ideak-mobl \
--to=imre.deak@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rob.clark@linaro.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;
as well as URLs for NNTP newsgroup(s).