[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vdi2c=s_z9wwxWzVcL+4tx5ZnXymbiN4O1FS+D3kz5vqw@mail.gmail.com>
Date: Wed, 28 Feb 2024 02:03:59 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Chris Packham <chris.packham@...iedtelesis.co.nz>
Cc: andy@...nel.org, geert@...ux-m68k.org, robh+dt@...nel.org,
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 Tue, Feb 27, 2024 at 11:22 PM Chris Packham
<chris.packham@...iedtelesis.co.nz> wrote:
..
> + segment-gpios:
> + description:
> + An array of GPIOs one per segment.
This is a vague description. Please explain the order (e.g., LSB =
'a', MSB = 'g'), use of DP (optional?), etc.
> + minItems: 7
maxItems?
..
> + led-7seg {
Probably it should be more human readable. DT people might suggest
something better.
> + compatible = "generic-gpio-7seg";
> + segment-gpios = <&gpio 0 GPIO_ACTIVE_LOW
> + &gpio 1 GPIO_ACTIVE_LOW
> + &gpio 2 GPIO_ACTIVE_LOW
> + &gpio 3 GPIO_ACTIVE_LOW
> + &gpio 4 GPIO_ACTIVE_LOW
> + &gpio 5 GPIO_ACTIVE_LOW
> + &gpio 6 GPIO_ACTIVE_LOW>;
Dunno how to handle DP. Either we always expect it to be here (as
placeholder) or with additional property.
> + };
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists