[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZeBfqTKVLp1YsJJG@smile.fi.intel.com>
Date: Thu, 29 Feb 2024 12:42:49 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Rob Herring <robh@...nel.org>,
Chris Packham <chris.packham@...iedtelesis.co.nz>,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
andrew@...n.ch, gregory.clement@...tlin.com,
sebastian.hesselbarth@...il.com, ojeda@...nel.org,
tzimmermann@...e.de, javierm@...hat.com, robin@...tonic.nl,
lee@...nel.org, pavel@....cz, devicetree@...r.kernel.org,
linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 2/4] dt-bindings: auxdisplay: Add bindings for generic
7 segment LED
On Thu, Feb 29, 2024 at 10:23:15AM +0100, Geert Uytterhoeven wrote:
> On Wed, Feb 28, 2024 at 3:58 PM Andy Shevchenko
> <andy.shevchenko@...il.com> wrote:
> > On Wed, Feb 28, 2024 at 4:04 PM Rob Herring <robh@...nel.org> wrote:
> > > On Wed, Feb 28, 2024 at 10:22:42AM +1300, Chris Packham wrote:
..
> > > > + segment-gpios:
> > > > + description:
> > > > + An array of GPIOs one per segment.
> > > > + minItems: 7
> > >
> > > How does one know which GPIO is which segment?
> >
> > I believe we need just to agree on this. Since anybody can shuffle
> > GPIOs in the DT, there is no need to support arbitrary orders. And
> > naturally 'a' is bit 0, 'g' is bit 6, 'dp' bit 7 if present.
>
> Note that there are no bits involved at this level, only GPIO specifiers.
Right, I meant the sequence in the array of GPIOs in the DT.
I implied that it maps 1:1 to the real bits in HW (in some cases).
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists