[lkml]   [2020]   [Jan]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/4] drm/msm: use firmware-name to find zap fw
From: Rob Clark <>

For devices which use zap fw to take the GPU out of secure mode on
reset, the firmware is likely to be signed with a device specific key.
Meaning that we can't have a single filesystem (or /lib/firmware) that
works on multiple devices.

So allow a firmware-name to be specified in the zap-shader node in dt.
This moves the zap-shader node out of the core sdm845.dtsi and into per-
device dts files. Which also removes the need for /delete-node/ in
sdm845-cheza.dtsi (as cheza devices do not use zap).

This aligns with how Bjorn has been handling the similar situation with
adsp/cdsp/mpss fw:

Rob Clark (4):
drm/msm: support firmware-name for zap fw (v2)
drm/msm: allow zapfw to not be specified in gpulist
dt-bindings: drm/msm/gpu: Document firmware-name
arm64: dts: sdm845: move gpu zap nodes to per-device dts

.../devicetree/bindings/display/msm/gpu.txt | 3 ++
arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 1 -
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 7 +++
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 7 +++
arch/arm64/boot/dts/qcom/sdm845.dtsi | 6 +--
.../boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 7 +++
drivers/gpu/drm/msm/adreno/adreno_gpu.c | 50 +++++++++++++++----
7 files changed, 64 insertions(+), 17 deletions(-)


 \ /
  Last update: 2020-01-12 20:55    [W:0.042 / U:1.400 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site