diff options
| author | Jeevan Shriram <jshriram@codeaurora.org> | 2014-03-26 19:47:49 -0700 |
|---|---|---|
| committer | David Keitel <dkeitel@codeaurora.org> | 2016-03-23 20:28:55 -0700 |
| commit | 01ea04c62e5cfd3e64058f21b31cbb9dd9073917 (patch) | |
| tree | 965551f386de0ecbc0cba4bbf79ff2c5eb5f10e1 /include/uapi/linux | |
| parent | 158fae494ddcd818eadec2e3014086a9a67fc8df (diff) | |
mdss: msm_fb: Allocate fb memory during mmap
Current design of display driver (overlay) is no more
using the physically contiguous memory for normal display
functionality.
However, we still need to be backward compatible for any client
using the legacy implementation (eg. pan display) functionality.
As soon as there is a mmap call, the allocation happens from
system heap and gets removed once the references to frame buffer
driver becomes NULL.
With this change one can remove the physically contiguous memory
which gets allocated at the boot time and the usage of physically
contiguous memory is optimized.
Change-Id: I1b6040187bda8095007faa4d9df7dc046aa30c6e
Signed-off-by: Jeevan Shriram <jshriram@codeaurora.org>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions