From: Hermes Zhang <Hermes.Zhang@axis.com>
To: Rob Herring <robh@kernel.org>, Hermes Zhang <Hermes.Zhang@axis.com>
Cc: "pavel@ucw.cz" <pavel@ucw.cz>, "dmurphy@ti.com" <dmurphy@ti.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lkml@axis.com" <lkml@axis.com>, kernel <kernel@axis.com>
Subject: Re: [PATCH v2 1/2] dt-binding: leds: Document leds-multi-gpio bindings
Date: Mon, 29 Mar 2021 06:03:05 +0000 [thread overview]
Message-ID: <f29fa789cef74d869db6728f90f28d50@XBOX01.axis.com> (raw)
In-Reply-To: 20210327181222.GA327657@robh.at.kernel.org
On 3/28/21 2:12 AM, Rob Herring wrote:
>> +
>> + led-gpios:
>> + description: Array of one or more GPIOs pins used to control the LED.
>> + minItems: 1
>> + maxItems: 8 # Should be enough
>> +
>> + led-states:
>> + description: |
>> + The array list the supported states here which will map to brightness
>> + from 0 to maximum. Each item in the array will present all the GPIOs
>> + value by bit.
>> + $ref: /schemas/types.yaml#/definitions/uint8-array
>> + minItems: 1
>> + maxItems: 256 # Should be enough
> Isn't this the same as the standard 'brightness-levels' from backlight
> binding? The index is the level and the value is the h/w specific
> setting.
Yes, it seems same.
Best Regards,
Hermes
next prev parent reply other threads:[~2021-03-29 6:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 5:27 [PATCH v2 0/2] New multiple GPIOs LED driver Hermes Zhang
2021-03-26 5:28 ` [PATCH v2 1/2] dt-binding: leds: Document leds-multi-gpio bindings Hermes Zhang
2021-03-27 18:12 ` Rob Herring
2021-03-29 6:03 ` Hermes Zhang [this message]
2021-03-26 5:28 ` [PATCH v2 2/2] leds: leds-multi-gpio: Add multiple GPIOs LED driver Hermes Zhang
2021-03-26 5:56 ` Alexander Dahl
2021-03-26 6:07 ` Hermes Zhang
2021-03-26 13:49 ` Pavel Machek
2021-03-29 6:00 ` Hermes Zhang
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=f29fa789cef74d869db6728f90f28d50@XBOX01.axis.com \
--to=hermes.zhang@axis.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=pavel@ucw.cz \
--cc=robh@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