From: Rob Clark <robdclark@chromium.org>
Date: Wed, 8 Jan 2020 00:28:41 +0000 (-0800)
Subject: dt-bindings: drm/msm/gpu: Document firmware-name
X-Git-Tag: v5.10.7~3266^2~8^2~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=57d6c2eb735a0e08d7e0bbd985ec3ebc5fcaf214;p=platform%2Fkernel%2Flinux-rpi.git

dt-bindings: drm/msm/gpu: Document firmware-name

The firmware-name property in the zap node can be used to specify a
device specific zap firmware.

Signed-off-by: Rob Clark <robdclark@chromium.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
---

diff --git a/Documentation/devicetree/bindings/display/msm/gpu.txt b/Documentation/devicetree/bindings/display/msm/gpu.txt
index 3e6cd3f..7edc298 100644
--- a/Documentation/devicetree/bindings/display/msm/gpu.txt
+++ b/Documentation/devicetree/bindings/display/msm/gpu.txt
@@ -33,6 +33,8 @@ Required properties:
 - zap-shader: For a5xx and a6xx devices this node contains a memory-region that
   points to reserved memory to store the zap shader that can be used to help
   bring the GPU out of secure mode.
+- firmware-name: optional property of the 'zap-shader' node, listing the
+  relative path of the device specific zap firmware.
 
 Example 3xx/4xx/a5xx:
 
@@ -85,6 +87,7 @@ Example a6xx (with GMU):
 
 		zap-shader {
 			memory-region = <&zap_shader_region>;
+			firmware-name = "qcom/LENOVO/81JL/qcdxkmsuc850.mbn"
 		};
 	};
 };