From: Pavel Machek <pavel@ucw.cz>
To: "Vesa Jääskeläinen" <dachaac@gmail.com>
Cc: Hermes Zhang <chenhui.zhang@axis.com>,
dmurphy@ti.com, robh+dt@kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
chenhuiz@axis.com, lkml@axis.com, kernel@axis.com
Subject: Re: [PATCH 2/2] dt-binding: leds: Document leds-multi-gpio bindings
Date: Thu, 25 Mar 2021 19:41:40 +0100 [thread overview]
Message-ID: <20210325184140.GA16039@duo.ucw.cz> (raw)
In-Reply-To: <0648fff2-5b38-66da-7eb0-9969e517421f@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Hi!
> See below.
Please trim.
> > + led-gpios:
> > + description: Array of one or more GPIOs pins used to control the LED.
> > + minItems: 1
> > + maxItems: 8 # Should be enough
>
> We also have a case with multi color LEDs (which is probably a more common
> than multi intensity LED. So I am wondering how these both could co-exist.
>
> From: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/leds/leds-gpio.yaml?h=v5.12-rc4#n58
>
> led-0 {
> gpios = <&mcu_pio 0 GPIO_ACTIVE_LOW>;
> linux,default-trigger = "disk-activity";
> function = LED_FUNCTION_DISK;
> };
>
> Now 'gpios' (and in LED context) and 'led-gpios' is very close to each other
> and could easily be confused.
>
> Perhaps this could be something like:
>
> intensity-gpios = ...
>
> or even simplified then just to gpios = <...>
...
> How would this sound?
Well, not too bad on a quick look.
Are you willing to implement such multi-color-multi-bit-multi-gpio
driver?
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-03-25 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 7:56 [PATCH 0/2] New multiple GPIOs LED driver Hermes Zhang
2021-03-24 7:56 ` [PATCH 1/2] leds: leds-multi-gpio: Add " Hermes Zhang
2021-03-24 10:34 ` Marek Behun
2021-03-24 10:40 ` Pavel Machek
2021-03-24 10:42 ` Pavel Machek
2021-03-25 6:04 ` Hermes Zhang
2021-03-25 12:26 ` Marek Behun
2021-03-24 10:41 ` Pavel Machek
2021-03-24 7:56 ` [PATCH 2/2] dt-binding: leds: Document leds-multi-gpio bindings Hermes Zhang
2021-03-24 10:40 ` Marek Behun
2021-03-25 5:27 ` Vesa Jääskeläinen
2021-03-25 18:41 ` Pavel Machek [this message]
2021-03-28 20:46 ` Vesa Jääskeläinen
2021-03-24 10:42 ` [PATCH 0/2] New multiple GPIOs LED driver Marek Behun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210325184140.GA16039@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=chenhui.zhang@axis.com \
--cc=chenhuiz@axis.com \
--cc=dachaac@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkml@axis.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).