summaryrefslogtreecommitdiff
path: root/include/uapi/linux/raid
diff options
context:
space:
mode:
authorAravind Venkateswaran <aravindh@codeaurora.org>2014-10-23 17:23:50 -0700
committerDavid Keitel <dkeitel@codeaurora.org>2016-03-23 20:35:58 -0700
commit0c111eb0ac5853aa3b308112590305593dc2dde4 (patch)
tree152c4d35009741b1b050650db28c1baf37a1c93f /include/uapi/linux/raid
parentb6d1c8645c5214d36e4900f1daf0f34edc4155f1 (diff)
msm: mdss: fix fb device pm suspend and resume handlers
Under normal circumstances, the framebuffer device should have been blanked or configured to a low power mode prior to the pm suspend callback getting executed. In cases when this sequence is not followed, blank the framebuffer as part of pm suspend handler to ensure that all display resources are freed. Similarly, if the framebuffer was explicitly blanked during suspend, then unblank it when resuming. This also eliminates the need for the existing sysfs node to indicate always-on display mode. Change-Id: I1613f5eba420c9587af2ecb04bc5cb115b7a1095 Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>
Diffstat (limited to 'include/uapi/linux/raid')
0 files changed, 0 insertions, 0 deletions