aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAmit Pundir <amit.pundir@linaro.org>2019-04-15 15:56:01 +0530
committerBjorn Andersson <bjorn.andersson@linaro.org>2019-10-02 23:32:55 -0700
commitd25000a6a24c91d1b436f81b9edd528f6ce3b29b (patch)
treef8cb2cef2e3d05d496d2ceb85c74aae168c18286
parent351ca03b08d9dc7fa3d5e1ba3de37c5e2ca53c91 (diff)
downloadkernel-tracking-qcomlt-sdm845-db845c.tar.gz
HACK: db845c: drm/bridge: lt9611: comment out lt9611_sleep_setup()tracking-qcomlt-sdm845-db845c
According to bamse: The connect/disconnect dance in dmesg doesn't look promising, but if for some reason your DRM HAL switches mode the failure would be "expected". So comment out the call to lt9611_sleep_setup() and it will at least ensure you won't get the "lt9611 10-003b: power on failed" error in dmesg. Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
-rw-r--r--drivers/gpu/drm/bridge/lt9611.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpu/drm/bridge/lt9611.c b/drivers/gpu/drm/bridge/lt9611.c
index 748ff21fcd17..e48645f3049c 100644
--- a/drivers/gpu/drm/bridge/lt9611.c
+++ b/drivers/gpu/drm/bridge/lt9611.c
@@ -931,7 +931,7 @@ static void lt9611_bridge_post_disable(struct drm_bridge *bridge)
dev_dbg(lt9611->dev, "bridge post_disable\n");
- lt9611_sleep_setup(lt9611);
+ //lt9611_sleep_setup(lt9611);
}
static void lt9611_bridge_mode_set(struct drm_bridge *bridge,