| Message ID | 1425413066-20757-3-git-send-email-robdclark@gmail.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On 3 March 2015 at 20:04, Rob Clark <robdclark@gmail.com> wrote: > Add a reserved-memory region for bootloader splashscreen, and assign it > to the display device, so that drm/msm can take over the bootloader's > splashscreen. > Hi Rob, Rather silly question - does the bootloader always use/preserve the same amount of memory regardless of the display's resolution & bpp ? If not would this patch work in such cases ? Cheers Emil -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Mar 4, 2015 at 6:10 PM, Emil Velikov <emil.l.velikov@gmail.com> wrote: > On 3 March 2015 at 20:04, Rob Clark <robdclark@gmail.com> wrote: >> Add a reserved-memory region for bootloader splashscreen, and assign it >> to the display device, so that drm/msm can take over the bootloader's >> splashscreen. >> > Hi Rob, > > Rather silly question - does the bootloader always use/preserve the > same amount of memory regardless of the display's resolution & bpp ? > If not would this patch work in such cases ? > In most cases, the bootloader puts up a splash screen on built-in lcd panel, which sort of makes the problem easier (fixed resolution). For external display, I think you just have to size it for worst-case (largest) resolution. (ofc it is RFC since I was hoping to get comments if anyone has better suggestions.. probably should have cc'd more people ;-)) BR, -R > Cheers > Emil -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 4 March 2015 at 23:19, Rob Clark <robdclark@gmail.com> wrote: > On Wed, Mar 4, 2015 at 6:10 PM, Emil Velikov <emil.l.velikov@gmail.com> wrote: >> On 3 March 2015 at 20:04, Rob Clark <robdclark@gmail.com> wrote: >>> Add a reserved-memory region for bootloader splashscreen, and assign it >>> to the display device, so that drm/msm can take over the bootloader's >>> splashscreen. >>> >> Hi Rob, >> >> Rather silly question - does the bootloader always use/preserve the >> same amount of memory regardless of the display's resolution & bpp ? >> If not would this patch work in such cases ? >> > > In most cases, the bootloader puts up a splash screen on built-in lcd > panel, which sort of makes the problem easier (fixed resolution). For > external display, I think you just have to size it for worst-case > (largest) resolution. > > (ofc it is RFC since I was hoping to get comments if anyone has better > suggestions.. probably should have cc'd more people ;-)) > I believe that Intel managed to get flicker-free boot. iirc Jess Barnes was one of the people working on it. That said I'm not sure how much of their work is applicable in non-x86 land :-\ -Emil -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts b/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts index 416f3f5..0928129 100644 --- a/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts +++ b/arch/arm/boot/dts/qcom-apq8064-ifc6410.dts @@ -15,6 +15,16 @@ 0x90000000 0x70000000>; }; + reserved-memory { + #address-cells = <1>; + #size-cells = <1>; + ranges; + + splashmem: framebuffer@90000000 { + reg = <0x90000000 0x800000>; + }; + }; + aliases { serial0 = &serial0; serial1 = &serial1; @@ -183,5 +193,9 @@ }; }; + + mdp: qcom,mdp@5100000 { + memory-region = <&splashmem>; + }; }; };
Add a reserved-memory region for bootloader splashscreen, and assign it to the display device, so that drm/msm can take over the bootloader's splashscreen. Signed-off-by: Rob Clark <robdclark@gmail.com> --- arch/arm/boot/dts/qcom-apq8064-ifc6410.dts | 14 ++++++++++++++ 1 file changed, 14 insertions(+)