diff options
| author | Dilip Kota <c_dkota@codeaurora.org> | 2014-01-28 21:42:01 +0530 |
|---|---|---|
| committer | Naveen Kaje <nkaje@codeaurora.org> | 2014-05-23 15:47:31 -0600 |
| commit | 1d1e6459e9bae517026171fceaef68a991bb42f0 (patch) | |
| tree | 7ad48475e1dbad2e6035d4bf9b1e2845e9d86b8a /scripts/gcc-wrapper.py | |
| parent | 24b914dc395fff7be014261a79044bfe7f916a11 (diff) | |
msm_serial_hs: Manage wake unlock delay
Current implementation of wake locks wait for
around 500msec while releasing the wakelock. This
prevents the system suspend for that much time after
the rx operation is done to ensure that all the data
delivered to the client before system suspend.
But some clients may take care of this in their
implementation. In this case uart driver no need to
wait before releasing the wakelock.
Hence, given the control to the client as a dtsi entry
to take decision on waiting before releasing the wakelock.
Change-Id: Ie32a0b76899963e7700ba378906fa4f9b3fa3ba4
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
Signed-off-by: Dilip Kota <c_dkota@codeaurora.org>
Diffstat (limited to 'scripts/gcc-wrapper.py')
0 files changed, 0 insertions, 0 deletions