Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1634343

Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali Midgard GPU

From Guillaume Tucker <guillaume.tucker@collabora.com>
Newsgroups linux.kernel
Subject Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali Midgard GPU
Date 2017-05-02 13:30 +0200
Message-ID <tCEad-64n-1@gated-at.bofh.it> (permalink)
References <tA8xP-5bb-11@gated-at.bofh.it> <tA8xP-5bb-9@gated-at.bofh.it> <tBjKy-3t4-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Rob,

On 28/04/17 20:27, Rob Herring wrote:
> On Tue, Apr 25, 2017 at 02:16:16PM +0100, Guillaume Tucker wrote:

>> diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt b/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt
>> new file mode 100644
>> index 000000000000..547ddeceb498
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt
>> @@ -0,0 +1,82 @@
>> +ARM Mali Midgard GPU
>> +====================
>> +
>> +Required properties:
>> +
>> +- compatible :
>> +  * Must be one of the following:
>> +    + "arm,mali-t60x"
>> +    + "arm,mali-t62x"
>
> Don't use wildcards.

Sure, old habits die hard...  I'll fix it in patch v5.

>> +    + "arm,mali-t720"
>> +    + "arm,mali-t760"
>> +    + "arm,mali-t820"
>> +    + "arm,mali-t830"
>> +    + "arm,mali-t860"
>> +    + "arm,mali-t880"
>> +  * And, optionally, one of the vendor specific compatible:
>
> IMO, these should not be optional.

Well, vendor compatible strings are clearly optional for the
Utgard GPU series for which the bindings docs were recently
merged.  It seems that whether these should be optional or not,
the documentation should be consistent between at least all
similar types of devices like Midgard and Utgard GPUs.  They have
different architectures but from a device tree point of view,
they both have the same kind of SoC-specific integration (clocks,
irqs, regulators...).

So was this was overlooked in the Utgard case and should it
ideally be fixed there as well as non-optional?  Or, is it OK to
keep these optional on a second thought?

>> +    + "amlogic,meson-gxm-mali"
>> +    + "rockchip,rk3288-mali"

Guillaume

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali Midgard GPU Guillaume Tucker <guillaume.tucker@collabora.com> - 2017-04-25 15:20 +0200
  Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali  Midgard GPU Rob Herring <robh@kernel.org> - 2017-04-28 21:30 +0200
    Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali  Midgard GPU Guillaume Tucker <guillaume.tucker@collabora.com> - 2017-05-02 13:30 +0200
      Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali  Midgard GPU Rob Herring <robh@kernel.org> - 2017-05-02 16:20 +0200
        Re: [PATCH v4 1/5] dt-bindings: gpu: add bindings for the ARM Mali  Midgard GPU Guillaume Tucker <guillaume.tucker@collabora.com> - 2017-05-02 17:00 +0200

csiph-web