Messages in this thread |  | | Date | Tue, 7 Jan 2020 20:57:48 -0800 | From | Bjorn Andersson <> | Subject | Re: [PATCH 2/3] dt-bindings: drm/msm/gpu: Document firmware-name |
| |
On Tue 07 Jan 17:38 PST 2020, Rob Clark wrote:
> From: Rob Clark <robdclark@chromium.org> > > 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>
> --- > Documentation/devicetree/bindings/display/msm/gpu.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/msm/gpu.txt b/Documentation/devicetree/bindings/display/msm/gpu.txt > index 3e6cd3f64a78..7edc298a15f2 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" > }; > }; > }; > -- > 2.24.1 >
|  |