From: Rahul Sharma <rahul.sharma@samsung.com>
To: dri-devel@lists.freedesktop.org
Cc: linux-samsung-soc@vger.kernel.org, inki.dae@samsung.com,
joshi@samsung.com, r.sh.open@gmail.com,
Rahul Sharma <rahul.sharma@samsung.com>
Subject: [PATCH] drm/exynos: fix nested calls to lock mutex in drm resume
Date: Wed, 30 Apr 2014 19:11:34 +0530 [thread overview]
Message-ID: <1398865294-6754-1-git-send-email-rahul.sharma@samsung.com> (raw)
From: Rahul Sharma <Rahul.Sharma@samsung.com>
While testing S2R on exynos board, system is hanging and
rebooting due to nested mutex_lock calls in exynos drm
resume callback. Changing the order of the calls is fixing
the issue.
Signed-off-by: Rahul Sharma <Rahul.Sharma@samsung.com>
---
Based on exynos-drm-next branch in Inki Dae's tree.
drivers/gpu/drm/exynos/exynos_drm_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/exynos/exynos_drm_drv.c b/drivers/gpu/drm/exynos/exynos_drm_drv.c
index bb7dfee..2bb6233 100644
--- a/drivers/gpu/drm/exynos/exynos_drm_drv.c
+++ b/drivers/gpu/drm/exynos/exynos_drm_drv.c
@@ -184,8 +184,8 @@ static int exynos_drm_resume(struct drm_device *dev)
connector->funcs->dpms(connector, connector->dpms);
}
- drm_helper_resume_force_mode(dev);
drm_modeset_unlock_all(dev);
+ drm_helper_resume_force_mode(dev);
return 0;
}
--
1.7.9.5
next reply other threads:[~2014-04-30 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 13:41 Rahul Sharma [this message]
2014-05-22 14:16 ` [PATCH] drm/exynos: fix nested calls to lock mutex in drm resume Rahul Sharma
2014-05-22 15:32 ` Kyungmin Park
2014-05-22 17:56 ` Sachin Kamat
2014-05-23 2:14 ` Rahul Sharma
-- strict thread matches above, loose matches on Subject: below --
2014-04-30 13:02 Rahul Sharma
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=1398865294-6754-1-git-send-email-rahul.sharma@samsung.com \
--to=rahul.sharma@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=r.sh.open@gmail.com \
/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.