[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <696316719.95315119.1575467579136.JavaMail.zimbra@kalray.eu>
Date: Wed, 4 Dec 2019 14:52:59 +0100 (CET)
From: Clément Leger <cleger@...ray.eu>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Hoan Tran <hoan@...amperecomputing.com>,
"open list, GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>
Subject: Re: [PATCH 5/5] dt-bindings: pinctrl: dw: move sps,dwapb-gpio.txt
to pinctrl
----- On 4 Dec, 2019, at 13:45, Andy Shevchenko andy.shevchenko@...il.com wrote:
> On Wed, Dec 4, 2019 at 12:13 PM Clement Leger <cleger@...ray.eu> wrote:
>>
>> Since the driver has been moved to pinctrl and now supports it, move the
>> documentation into pinctrl folder. In the same time, add documentation
>> for pinctrl properties such has snps,has-pinctrl and description of pin
>> alternate functions.
>
>> +- snps,has-pinctrl : If present, register the pinctrl controller.
>
> I'm wondering why we can't always assume pin control?
This hardware IP is configured when instantiated to include support for
muxing. If configured without support, the registers will exists but won't
configure anything.
I guess that it's not really a problem but it will lead to unusable
pin muxing.
>
>> -F: Documentation/devicetree/bindings/gpio/snps-dwapb-gpio.txt
>> +F: Documentation/devicetree/bindings/pinctrl/snps-dwapb-gpio.txt
>
> I guess this should be a part of patch 2 when you move driver w/o
> changes to a new folder.
Agreed. I will do that,
Thanks
>
> --
> With Best Regards,
> Andy Shevchenko
Powered by blists - more mailing lists