From: Rob Herring <robh@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Pavel Machek" <pavel@ucw.cz>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Marek Behún" <kabel@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: leds: register-bit-led: Add value property
Date: Wed, 6 Jul 2022 10:21:11 -0600 [thread overview]
Message-ID: <20220706162111.GA145516-robh@kernel.org> (raw)
In-Reply-To: <20220706112828.27278-1-pali@kernel.org>
On Wed, Jul 06, 2022 at 01:28:27PM +0200, Pali Rohár wrote:
> Allow to define inverted logic (0 - enable LED, 1 - disable LED) via value
> property. This property name is already used by other syscon drivers, e.g.
> syscon-reboot.
Yes, but those are potentially multi-bit values. This is a single bit
value, and the only value that's ever needed is 0. Why not just use
'active-low' here?
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
> ---
> .../devicetree/bindings/leds/register-bit-led.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/leds/register-bit-led.yaml b/Documentation/devicetree/bindings/leds/register-bit-led.yaml
> index 79b8fc0f9d23..d6054a3f9087 100644
> --- a/Documentation/devicetree/bindings/leds/register-bit-led.yaml
> +++ b/Documentation/devicetree/bindings/leds/register-bit-led.yaml
> @@ -43,6 +43,17 @@ properties:
> 0x100000, 0x200000, 0x400000, 0x800000, 0x1000000, 0x2000000, 0x4000000,
> 0x8000000, 0x10000000, 0x20000000, 0x40000000, 0x80000000 ]
>
> + value:
> + description:
> + bit value of ON state for the bit controlling this LED in the register
> + when not specified it is same as the mask
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum:
> + [ 0x0, 0x1, 0x2, 0x4, 0x8, 0x10, 0x20, 0x40, 0x80, 0x100, 0x200, 0x400, 0x800,
> + 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000, 0x40000, 0x80000,
> + 0x100000, 0x200000, 0x400000, 0x800000, 0x1000000, 0x2000000, 0x4000000,
> + 0x8000000, 0x10000000, 0x20000000, 0x40000000, 0x80000000 ]
> +
> offset:
> description:
> register offset to the register controlling this LED
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2022-07-06 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 11:28 [PATCH 1/2] dt-bindings: leds: register-bit-led: Add value property Pali Rohár
2022-07-06 11:28 ` [PATCH 2/2] leds: syscon: Implement support for " Pali Rohár
2022-07-06 16:21 ` Rob Herring [this message]
2022-07-06 16:23 ` [PATCH 1/2] dt-bindings: leds: register-bit-led: Add " Pali Rohár
2022-07-11 12:06 ` Linus Walleij
2022-07-11 12:10 ` Pali Rohár
2022-07-11 12:21 ` Linus Walleij
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=20220706162111.GA145516-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kabel@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pali@kernel.org \
--cc=pavel@ucw.cz \
/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).