[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZvJmH61C8Rd3TeTioag+11GHPGdCDwRHxx3UAzB-rUHg@mail.gmail.com>
Date: Thu, 15 Nov 2018 10:43:05 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Andrei.Stefanescu@...rochip.com
Cc: Greg KH <gregkh@...uxfoundation.org>,
Nicolas Ferre <Nicolas.Ferre@...rochip.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Ludovic Desroches <Ludovic.Desroches@...rochip.com>,
Cristian.Birsan@...rochip.com,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>
Subject: Re: [PATCH 1/3] dt-bindings: gpio: add sama5d2 PIOBU support
On Wed, Nov 7, 2018 at 4:12 PM <Andrei.Stefanescu@...rochip.com> wrote:
> +Required properties:
> +- compatible: "syscon", "microchip,sama5d2-piobu"
Looks like "syscon" should be dropped, it is using a syscon,
but it is no syscon.
> + secumod@...40000 {
> + compatible = "syscon", "microchip,sama5d2-piobu";
> + reg = <0xfc040000 0x100>;
> +
> + gpio-controller;
> + #gpio-cells = <2>;
> + };
Isn't it easiest to just make this driver be a subnode of the
syscon so it can just refer to its parent to find the
syscon it needs?
Just state that in the bindings and make an example where
it is inside the syscon.
Yours,
Linus Walleij
Powered by blists - more mailing lists