[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200108013847.899170-1-robdclark@gmail.com>
Date: Tue, 7 Jan 2020 17:38:41 -0800
From: Rob Clark <robdclark@...il.com>
To: dri-devel@...ts.freedesktop.org
Cc: devicetree@...r.kernel.org, freedreno@...ts.freedesktop.org,
linux-arm-msm@...r.kernel.org,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Jordan Crouse <jcrouse@...eaurora.org>,
Sharat Masetty <smasetty@...eaurora.org>,
Rob Clark <robdclark@...omium.org>,
Brian Masney <masneyb@...tation.org>,
Douglas Anderson <dianders@...omium.org>,
Fabio Estevam <festevam@...il.com>,
Jeffrey Hugo <jeffrey.l.hugo@...il.com>,
linux-kernel@...r.kernel.org (open list),
Thomas Gleixner <tglx@...utronix.de>
Subject: [PATCH 0/3] drm/msm: use firmware-name to find zap fw
From: Rob Clark <robdclark@...omium.org>
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:
https://patchwork.kernel.org/patch/11160089/
Rob Clark (3):
drm/msm: support firmware-name for zap fw
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 | 8 +++++
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 | 32 +++++++++++++++++--
7 files changed, 55 insertions(+), 9 deletions(-)
--
2.24.1
Powered by blists - more mailing lists