On Sat, Jul 3, 2021 at 8:20 AM David Heidelberg <david@xxxxxxx> wrote: > > This warning cannot be fixed by conversion, since this naming is already used. > Documentation/devicetree/bindings/display/msm/gpu.example.dt.yaml: gpu@5000000: interconnect-names: ['gfx-mem'] is too short > > Signed-off-by: David Heidelberg <david@xxxxxxx> > --- > .../devicetree/bindings/display/msm/gpu.txt | 157 ----------- > .../devicetree/bindings/display/msm/gpu.yaml | 256 ++++++++++++++++++ > 2 files changed, 256 insertions(+), 157 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/display/msm/gpu.txt > create mode 100644 Documentation/devicetree/bindings/display/msm/gpu.yaml > > diff --git a/Documentation/devicetree/bindings/display/msm/gpu.txt b/Documentation/devicetree/bindings/display/msm/gpu.txt > deleted file mode 100644 [snip] > diff --git a/Documentation/devicetree/bindings/display/msm/gpu.yaml b/Documentation/devicetree/bindings/display/msm/gpu.yaml > new file mode 100644 > index 000000000000..4315482e0b12 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/msm/gpu.yaml [snip] > + zap-shader: > + description: | > + 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. > + Side note, this node is optional now, we do have some a6xx devices out there which do not use/require a zap shader (in particular, the chromebooks). Not sure if that effects how you want to document it in the yaml. Also, new dts for devices that use zap, they should specify a "firmware-name", since the zap shader is usually signed with a board specific signing key. BR, -R
