From: Your Name <you@example.com>
To: linux-kernel@vger.kernel.org
Cc: briannorris@chromium.org, dianders@chromium.org,
tfiga@chromium.org, seanpaul@chromium.org, zyw@rock-chips.com,
mark.yao@rock-chips.com, Jeffy Chen <jeffy.chen@rock-chips.com>,
Your Name <you@example.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Yakir Yang <kuankuan.y@gmail.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
Archit Taneja <architt@codeaurora.org>
Subject: [PATCH v4 02/12] drm: bridge: analogix: Unregister dp aux when unbinding
Date: Thu, 6 Apr 2017 20:22:13 +0800 [thread overview]
Message-ID: <1491481343-11025-3-git-send-email-you@example.com> (raw)
In-Reply-To: <1491481343-11025-1-git-send-email-you@example.com>
From: Jeffy Chen <jeffy.chen@rock-chips.com>
The dp aux is registered when binding analogix dp.
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
Signed-off-by: Your Name <you@example.com>
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/gpu/drm/bridge/analogix/analogix_dp_core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
index 28144a1..7b75f82 100644
--- a/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
+++ b/drivers/gpu/drm/bridge/analogix/analogix_dp_core.c
@@ -1447,6 +1447,7 @@ void analogix_dp_unbind(struct device *dev, struct device *master,
DRM_ERROR("failed to detach the panel\n");
}
+ drm_dp_aux_unregister(&dp->aux);
pm_runtime_disable(dev);
}
EXPORT_SYMBOL_GPL(analogix_dp_unbind);
--
2.1.4
next prev parent reply other threads:[~2017-04-06 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 12:22 [PATCH v4 00/12] drm: rockchip: Fix rockchip drm unbind crash error Your Name
2017-04-06 12:22 ` [PATCH v4 01/12] drm: bridge: analogix: Detach panel when unbinding analogix dp Your Name
2017-04-06 12:22 ` Your Name [this message]
2017-04-06 12:22 ` [PATCH v4 03/12] drm: bridge: analogix: Disable clock when unbinding Your Name
2017-04-06 12:22 ` [PATCH v4 04/12] drm: bridge: analogix: Destroy connector & encoder " Your Name
2017-04-06 12:22 ` [PATCH v4 05/12] drm/rockchip: cdn-dp: Don't try to release firmware when not loaded Your Name
2017-04-06 12:22 ` [PATCH v4 06/12] drm/rockchip: cdn-dp: Don't unregister audio dev when unbinding Your Name
2017-04-06 12:22 ` [PATCH v4 07/12] drm/rockchip: vop: Enable pm domain before vop_initial Your Name
2017-04-06 12:22 ` [PATCH v4 08/12] drm/rockchip: vop: Unprepare clocks when unbinding Your Name
2017-04-06 12:22 ` [PATCH v4 09/12] drm/rockchip: analogix_dp: Disable clock " Your Name
2017-04-06 12:22 ` [PATCH v4 10/12] drm/rockchip: Reoder drm bind/unbind sequence Your Name
2017-04-06 12:22 ` [PATCH v4 11/12] drm/rockchip: Shutdown all crtcs when unbinding drm Your Name
2017-04-06 12:22 ` [PATCH v4 12/12] drm/drm_ioctl.c: Break ioctl when drm device not registered Your Name
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=1491481343-11025-3-git-send-email-you@example.com \
--to=you@example.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeffy.chen@rock-chips.com \
--cc=kuankuan.y@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mark.yao@rock-chips.com \
--cc=seanpaul@chromium.org \
--cc=tfiga@chromium.org \
--cc=tomeu.vizoso@collabora.com \
--cc=zyw@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox