From: Rob Herring <robh@kernel.org>
To: sven@svenschwermer.de
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org,
Sven Schwermer <sven.schwermer@disruptive-technologies.com>,
pavel@ucw.cz, thierry.reding@gmail.com,
u.kleine-koenig@pengutronix.de, lee.jones@linaro.org,
post@lespocky.de, andy.shevchenko@gmail.com
Subject: Re: [PATCH v6 2/3] dt-bindings: leds: Add multicolor PWM LED bindings
Date: Wed, 9 Feb 2022 12:44:49 -0600 [thread overview]
Message-ID: <YgQLoaKmzfZQAVSx@robh.at.kernel.org> (raw)
In-Reply-To: <20220208191236.660172-2-sven@svenschwermer.de>
On Tue, Feb 08, 2022 at 08:12:35PM +0100, sven@svenschwermer.de wrote:
> From: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
>
> This allows to group multiple PWM-connected monochrome LEDs into
> multicolor LEDs, e.g. RGB LEDs.
>
> Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> ---
>
> Notes:
> Changes in v6:
> * Fix device tree binding schema
>
> Changes in v5:
> * (no changes)
>
> Changes in v4:
> * (no changes)
>
> Changes in v3:
> * Remove multi-led unit name
>
> .../bindings/leds/leds-pwm-multicolor.yaml | 69 +++++++++++++++++++
> 1 file changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml b/Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml
> new file mode 100644
> index 000000000000..f7ce29c8ae63
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/leds-pwm-multicolor.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/leds/leds-pwm-multicolor.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Multi-color LEDs connected to PWM
> +
> +maintainers:
> + - Sven Schwermer <sven.schwermer@disruptive-technologies.com>
> +
> +description: |
> + This driver combines several monochrome PWM LEDs into one multi-color
> + LED using the multicolor LED class.
> +
> +properties:
> + compatible:
> + const: pwm-leds-multicolor
blank line
> + multi-led:
> + type: object
blank line
> + patternProperties:
> + "^led-[0-9a-z]+$":
> + type: object
> + $ref: common.yaml#
blank line
> + properties:
> + pwms:
> + maxItems: 1
blank line and so on. (There not a hard rule, but roughly it's
blank lines between DT property sub-schemas, top-level keywords, and
properties/patternProperties/required.)
> + pwm-names: true
> + color: true
> + required:
> + - pwms
> + - color
> + additionalProperties: false
While the top level goes at the end, I find it is easier to read putting
the indented cases before properties/patternProperties.
> +required:
> + - compatible
> +allOf:
> + - $ref: leds-class-multicolor.yaml#
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + rgb-led {
> + compatible = "pwm-leds-multicolor";
> +
> + multi-led {
> + color = <LED_COLOR_ID_RGB>;
> + function = LED_FUNCTION_INDICATOR;
> + max-brightness = <65535>;
> +
> + led-red {
> + pwms = <&pwm1 0 1000000>;
> + color = <LED_COLOR_ID_RED>;
> + };
> +
> + led-green {
> + pwms = <&pwm2 0 1000000>;
> + color = <LED_COLOR_ID_GREEN>;
> + };
> +
> + led-blue {
> + pwms = <&pwm3 0 1000000>;
> + color = <LED_COLOR_ID_BLUE>;
> + };
> + };
> + };
> +
> +...
> --
> 2.35.1
>
>
next prev parent reply other threads:[~2022-02-09 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:12 [PATCH v6 1/3] dt-bindings: leds: Optional multi-led unit address sven
2022-02-08 19:12 ` [PATCH v6 2/3] dt-bindings: leds: Add multicolor PWM LED bindings sven
2022-02-09 9:17 ` Alexander Dahl
2022-02-10 7:55 ` Sven Schwermer
2022-02-10 9:33 ` Alexander Dahl
2022-02-11 19:37 ` Sven Schwermer
2022-02-09 18:44 ` Rob Herring [this message]
2022-02-08 19:12 ` [PATCH v6 3/3] leds: Add PWM multicolor driver sven
2022-02-09 18:35 ` [PATCH v6 1/3] dt-bindings: leds: Optional multi-led unit address Rob Herring
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=YgQLoaKmzfZQAVSx@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=post@lespocky.de \
--cc=sven.schwermer@disruptive-technologies.com \
--cc=sven@svenschwermer.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).