[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdY_1-4QPzuQs0aqX4M=RDzT3y9m7FTA_Dq71vEn22A8qw@mail.gmail.com>
Date: Wed, 26 Apr 2023 22:48:20 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Rob Herring <robh@...nel.org>
Cc: Nikita Shubin <nikita.shubin@...uefel.me>,
Arnd Bergmann <arnd@...nel.org>,
Linus Walleij <linusw@...nel.org>,
Alexander Sverdlin <alexander.sverdlin@...il.com>,
Bartosz Golaszewski <brgl@...ev.pl>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 32/43] dt-bindings: gpio: Add DT bindings ep93xx gpio
On Mon, Apr 24, 2023 at 6:32 PM Rob Herring <robh@...nel.org> wrote:
> On Mon, Apr 24, 2023 at 03:34:48PM +0300, Nikita Shubin wrote:
> > Add YAML bindings for ep93xx SoC.
> >
> > Signed-off-by: Nikita Shubin <nikita.shubin@...uefel.me>
(...)
> > + chip-label:
> > + maxItems: 1
> > + description: human readable name.
>
> Why do you need this? It's not standard and I don't see other GPIO
> controllers needing it.
Caught my eye too, Nikita can you live without this and just use dev_name()
or something to name the chip in Linux?
If it is to conform to EP93xx documentation naming I guess it should be
cirrus,ep93xx-gpio-chip-name = "..."; ?
Yours,
Linus Walleij
Powered by blists - more mailing lists