diff options
| author | Dhaval Patel <pdhaval@codeaurora.org> | 2014-08-18 12:57:19 -0700 |
|---|---|---|
| committer | David Keitel <dkeitel@codeaurora.org> | 2016-03-23 20:33:22 -0700 |
| commit | c05ee5a7cdf5b264aa73e30c2003d6a65fb74cb4 (patch) | |
| tree | 33acb1d6e2756e8226de30f37f30e072cad9e861 /Documentation/devicetree | |
| parent | 67ac4262d4222fe770f1e94b8baae4aa8324dc51 (diff) | |
mdss: mdp: parse memory handle for cont splash buffer
Continuous splash screen buffer is reserved in
target dtsi file for MSM8994 target. FB driver should
parse this memory handle using "linux,continuous-region"
to get the splash screen buffer address and size. This
avoids usage of "qcom,memory-reserve" entry which forces
user to provide duplicate information.
Change-Id: Ice6cddf6c71a2de9adf15a763434a310e07a3da6
Signed-off-by: Dhaval Patel <pdhaval@codeaurora.org>
Diffstat (limited to 'Documentation/devicetree')
| -rw-r--r-- | Documentation/devicetree/bindings/fb/mdss-mdp.txt | 18 |
1 files changed, 14 insertions, 4 deletions
diff --git a/Documentation/devicetree/bindings/fb/mdss-mdp.txt b/Documentation/devicetree/bindings/fb/mdss-mdp.txt index 0baf2991bc36..f1390f553938 100644 --- a/Documentation/devicetree/bindings/fb/mdss-mdp.txt +++ b/Documentation/devicetree/bindings/fb/mdss-mdp.txt @@ -424,11 +424,18 @@ Subnode properties: for the framebuffer used to display the splash screen. This property is required whenever the continuous splash screen feature is enabled for the corresponding - framebuffer device. + framebuffer device. It should be used for only 32bit + kernel. +- qcom,cont-splash-memory: Specifies the memory block region reserved for + continuous splash screen feature. This property should be + defined for corresponding framebuffer device if + "qcom,memblock-reserve" is not defined when continuous + splash screen feature is enabled. - linux,contiguous-region: Phandle to the continuous memory region reserved for - frame-buffer. Size of this region is dependent on the - display panel resolution and buffering scheme. - Currently driver uses double buffering. + frame-buffer or continuous splash screen. Size of this + region is dependent on the display panel resolution and + buffering scheme for frame-buffer node. Currently driver + uses double buffering. Example: Width = 1920, Height = 1080, BytesPerPixel = 4, Number of frame-buffers reserved = 2. @@ -578,6 +585,9 @@ Example: qcom,mdss-fb-split = <480 240> linux,contiguous-region = <&fb_mem>; qcom,mdss-fb-splash-logo-enabled: + qcom,cont-splash-memory { + linux,contiguous-region = <&cont_splash_mem>; + }; }; }; |