[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYE+u1o_KDDihX7=7RLNDkkFDOCFsQtBKBZW0i6123ZoQ@mail.gmail.com>
Date: Thu, 21 Dec 2017 10:18:28 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Alexandre Torgue <alexandre.torgue@...com>
Cc: Ludovic Barre <ludovic.Barre@...com>,
Russell King <linux@...linux.org.uk>,
Rob Herring <robh+dt@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Gerald Baeza <gerald.baeza@...com>,
Linux ARM <linux-arm-kernel@...ts.infradead.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 V2 9/9] ARM: dts: stm32: add initial support of
stm32mp157c eval board
On Wed, Dec 20, 2017 at 10:19 AM, Alexandre Torgue
<alexandre.torgue@...com> wrote:
> On 12/20/2017 08:44 AM, Linus Walleij wrote:
>> gpio-line-names = "foo", "bar" ...;
>>
>> See for example
>> arch/arm/boot/dts/bcm2835-rpi-a.dts
>> arch/arm/boot/dts/ste-snowball.dts
(...)
>
> It looks like useful for pins used as gpio line. Are you saying that we also
> have to describe pins used as Alternate Function ?
No. The use of the names is up to the platform maintainer (you),
leaving a blank string for non-GPIO lines is just fine.
Some platforms add the name of the actual function used by the
line on the design, if it is not GPIO, sometimes something in
brachets like "[i2c0-SDA]" that says what it is used for and explains
why you can't use it for GPIO on this setup.
But just leaving it blank is just as good.
Yours,
Linus Walleij
Powered by blists - more mailing lists