[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbbbbO-94i-ZTSunzuUQcJ8dQpuPHBYODrvdWQyuri7yw@mail.gmail.com>
Date: Mon, 2 Jul 2018 15:45:39 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Anson Huang <Anson.Huang@....com>,
Fabio Estevam <fabio.estevam@....com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
NXP Linux Team <Linux-imx@....com>
Subject: Re: [PATCH] bindings: add clocks optional binding for imx gpio
On Fri, Jun 29, 2018 at 5:34 AM Anson Huang <Anson.Huang@....com> wrote:
> Some i.MX SoCs have GPIO clock gate in CCM, accessing
> GPIO registers needs to enable GPIO clock gate first,
> i.MX GPIO driver will enable clock gate if there is
> clock property in GPIO node of dtb, add optional property
> to i.MX GPIO binding doc.
>
> Signed-off-by: Anson Huang <Anson.Huang@....com>
Make sense since the gpio-mxc driver already supports this :)
> +Optional properties:
> +- clocks: the clocks used by gpio bank
Should the text be "the clock for clocking the GPIO silicon"
I guess that is what it is. And singularis?
Does it hurt to give the clock a name? Like the common
"pclk" for peripheral clock or something similar that other
i.MX silicon uses?
Fabio: can we have your ACK on this too.
Yours,
Linus Walleij
Powered by blists - more mailing lists