summaryrefslogtreecommitdiff
path: root/drivers/slimbus/slim-msm.h
diff options
context:
space:
mode:
authorSagar Dharia <sdharia@codeaurora.org>2015-12-04 16:44:49 -0700
committerDavid Keitel <dkeitel@codeaurora.org>2016-03-23 21:13:24 -0700
commited2fedf0a5d087656530676d63d8b3ba6deacbcd (patch)
tree1fcab9a857480f8b02a4ca13e7038b91008a5af4 /drivers/slimbus/slim-msm.h
parent37808f8eceb2fbf549c03f79817d674590a3ff1c (diff)
slim_msm: Gracefully handle QMI timeout failures
QMI timeout can happen if other processor doesn't respond within the time expected by slimbus driver on apps. It has been noticed that QMI call to power-on slimbus rarely takes more than 500msec. Timeout is increased to allow that possibility. Additionally, QMI channel is drained out of left-over messages and runtime-PM state check is modified to allow graceful handling of timeout if at all any timeout still happens. Change-Id: I392a4fa761735135a261fb543815823cee5eba41 Signed-off-by: Sagar Dharia <sdharia@codeaurora.org>
Diffstat (limited to 'drivers/slimbus/slim-msm.h')
-rw-r--r--drivers/slimbus/slim-msm.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/slimbus/slim-msm.h b/drivers/slimbus/slim-msm.h
index 15c12ff580e4..86d2606182fa 100644
--- a/drivers/slimbus/slim-msm.h
+++ b/drivers/slimbus/slim-msm.h
@@ -96,7 +96,7 @@
#define SLIMBUS_QMI_INS_ID 0
/* QMI response timeout of 500ms */
-#define SLIM_QMI_RESP_TOUT 500
+#define SLIM_QMI_RESP_TOUT 1000
#define PGD_THIS_EE(r, v) ((v) ? PGD_THIS_EE_V2(r) : PGD_THIS_EE_V1(r))
#define PGD_PORT(r, p, v) ((v) ? PGD_PORT_V2(r, p) : PGD_PORT_V1(r, p))