lkml.org 
[lkml]   [2018]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH 2/2] dt-bindings: gpu: add Allwinner H6 Mali Midgard binding
    On Mon, Dec 3, 2018 at 6:25 AM Heiko Stuebner <heiko@sntech.de> wrote:
    >
    > Am Dienstag, 27. November 2018, 08:42:49 CET schrieb Icenowy Zheng:
    > > Allwinner H6 SoC uses a Mali T720 GPU, which is one of the GPUs in the
    > > Midgard GPU product line.
    > >
    > > Add binding for the H6 Mali Midgard GPU.
    > >
    > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
    > > ---
    > > .../devicetree/bindings/gpu/arm,mali-midgard.txt | 13 +++++++++++++
    > > 1 file changed, 13 insertions(+)
    > >
    > > diff --git a/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt b/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt
    > > index 02f870cd60e6..c897dd7be48f 100644
    > > --- a/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt
    > > +++ b/Documentation/devicetree/bindings/gpu/arm,mali-midgard.txt
    > > @@ -18,6 +18,7 @@ Required properties:
    > > + "amlogic,meson-gxm-mali"
    > > + "rockchip,rk3288-mali"
    > > + "rockchip,rk3399-mali"
    > > + + "allwinner,sun50i-h6-mali"
    >
    > I'd think you might want to keep an alphabetical sorting here, aka
    > above amlogic, otherwise the list will probably become hard to read
    > at some later point.
    >
    >
    > > - reg : Physical base address of the device and length of the register area.
    > >
    > > @@ -44,6 +45,18 @@ Optional properties:
    > > for details.
    > >
    > >
    > > +Vendor-specific bindings
    > > +------------------------
    > > +
    > > +The Mali GPU is integrated very differently from one SoC to
    > > +another. In order to accomodate those differences, you have the option
    > > +to specify one more vendor-specific compatible, among:
    > > +
    > > + - allwinner,sun50i-h6-mali
    > > + Required properties:
    > > + * resets: phandle to the reset line for the GPU
    >
    > While this paragraph is similar to how it is done in Utgard, I'm
    > wondering why we cannot just describe the "resets" as regular
    > optional property above that.

    Optional is fine, but I don't want to see every vendor doing their own
    definition (there's a similar patch for meson[1]). Please first figure
    out how many resets the IP block has. ARM should help as they were
    eager for me to accept this binding in the first place. Then we can
    see if vendors have extra resets.

    Rob

    [1] https://patchwork.ozlabs.org/patch/1010406/

    \
     
     \ /
      Last update: 2018-12-11 18:05    [W:3.028 / U:1.104 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site