Skip to content

arm64: boot: dts: qcom: sm8150: enable framebuffer for Surface Duo

Felipe Balbi linux-arm-msm linux-devicetree lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2arm64: boot: dts: qcom: sm8150: add a label for reserved-memoryarch/arm64/boot/dts/qcom/sm8150.dtsi+1 -10 replies
2/2arm64: boot: dts: qcom: surface duo: add minimal framebufferarch/arm64/boot/dts/qcom/sm8150-microsoft-surface-duo.dts+19 -03 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC/patch 0/2] arm64: boot: dts: qcom: sm8150: enable framebuffer for Surface Duo

From: Felipe Balbi <[email protected]>

Hi folks,

I'm trying to enable the framebuffer on Microsoft Surface Duo. Looking through some internal docs, it came to my attention that the bootloader will fill up the framebuffer address and size to a memory node names splash_region. Adding the node, I can see the address of the framebuffer. Creating the relevant framebuffer device using simple-framebuffer, I can't see it working. Tried dd if=/dev/urandom of=/dev/fb0 and fb-test. None of which manage to get rid of what's already on the screen, put there by the bootloader (platform Logo).

Wondering if any of you have seen a behavior such as this and how did you manage to get framebuffer working on SM8150 (I see at least Sony Xperia has the node).

Felipe Balbi (2):
arm64: boot: dts: qcom: sm8150: add a label for reserved-memory
arm64: boot: dts: qcom: surface duo: add minimal framebuffer

 .../dts/qcom/sm8150-microsoft-surface-duo.dts | 19 +++++++++++++++++++
 arch/arm64/boot/dts/qcom/sm8150.dtsi          |  2 +-
 2 files changed, 20 insertions(+), 1 deletion(-)
Signature · 1 line
2.34.1