From: Rob Herring <robh@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-realtek-soc@lists.infradead.org,
linux-leds@vger.kernel.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, zypeng@titanmec.com,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [RFC 06/25] dt-bindings: leds: Add Titan Micro Electronics TM1628
Date: Thu, 19 Dec 2019 17:04:20 -0600 [thread overview]
Message-ID: <20191219230335.GA25461@bogus> (raw)
In-Reply-To: <20191212033952.5967-7-afaerber@suse.de>
On Thu, Dec 12, 2019 at 04:39:33AM +0100, Andreas Färber wrote:
> Add a YAML schema binding for TM1628 LED controller.
>
> Cc: zypeng@titanmec.com
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> @Rob: How could we express constraints on two-cell reg value ranges here?
It's encoded as a matrix, so something like this:
reg:
items:
items:
- # constraints on 1st cell value
- # constraints on 2nd cell value
> Should we also model constraints on reg range by #grids property?
So the value of #grid defines the max values in reg? Unfortunately,
we can't yet for json-schema. There's been some proposals, but nothing
final I think.
> .../devicetree/bindings/leds/titanmec,tm1628.yaml | 80 ++++++++++++++++++++++
> 1 file changed, 80 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
>
> diff --git a/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml b/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
> new file mode 100644
> index 000000000000..024875656e79
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
> @@ -0,0 +1,80 @@
> +# SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/leds/titanmec,tm1628.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Titan Micro Electronics TM1628 LED controller
> +
> +maintainers:
> + - Andreas Färber <afaerber@suse.de>
> +
> +properties:
> + compatible:
> + enum:
> + - titanmec,tm1628
> +
> + reg:
> + maxItems: 1
> +
> + "#grids":
I'd be more a fan of using '#' prefix if we'd been better at using it
when appropriate, so I'd probably drop the '#'.
> + description: |
> + Number of GRID output lines to use.
> + This limits the number of available SEG output lines.
> + minimum: 4
> + maximum: 7
> +
> + "#address-cells":
> + const: 2
> +
> + "#size-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> +
> +patternProperties:
> + "^.*@[1-7],([1-9]|1[02-4])$":
> + type: object
> + description: |
> + Properties for a single LED.
Please describe the unit-address format. I assume it's <grid>,<segment>.
> +
> + properties:
> + reg:
> + description: |
> + 1-based grid number, followed by 1-based segment number.
> + maxItems: 1
> +
> + linux,default-trigger: true
> +
> + required:
> + - reg
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + led-controller@0 {
> + compatible = "titanmec,tm1628";
> + reg = <0>;
> + spi-3-wire;
> + spi-lsb-first;
> + spi-max-frequency = <500000>;
> + #grids = <7>;
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + colon@5,4 {
> + reg = <5 4>;
> + color = <LED_COLOR_ID_WHITE>;
> + function = LED_FUNCTION_INDICATOR;
> + linux,default-trigger = "heartbeat";
> + };
> + };
> + };
> +...
> --
> 2.16.4
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
linux-realtek-soc@lists.infradead.org,
linux-kernel@vger.kernel.org, Dan Murphy <dmurphy@ti.com>,
Pavel Machek <pavel@ucw.cz>,
zypeng@titanmec.com, linux-leds@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jacek Anaszewski <jacek.anaszewski@gmail.com>
Subject: Re: [RFC 06/25] dt-bindings: leds: Add Titan Micro Electronics TM1628
Date: Thu, 19 Dec 2019 17:04:20 -0600 [thread overview]
Message-ID: <20191219230335.GA25461@bogus> (raw)
In-Reply-To: <20191212033952.5967-7-afaerber@suse.de>
On Thu, Dec 12, 2019 at 04:39:33AM +0100, Andreas Färber wrote:
> Add a YAML schema binding for TM1628 LED controller.
>
> Cc: zypeng@titanmec.com
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> @Rob: How could we express constraints on two-cell reg value ranges here?
It's encoded as a matrix, so something like this:
reg:
items:
items:
- # constraints on 1st cell value
- # constraints on 2nd cell value
> Should we also model constraints on reg range by #grids property?
So the value of #grid defines the max values in reg? Unfortunately,
we can't yet for json-schema. There's been some proposals, but nothing
final I think.
> .../devicetree/bindings/leds/titanmec,tm1628.yaml | 80 ++++++++++++++++++++++
> 1 file changed, 80 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
>
> diff --git a/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml b/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
> new file mode 100644
> index 000000000000..024875656e79
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/titanmec,tm1628.yaml
> @@ -0,0 +1,80 @@
> +# SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/leds/titanmec,tm1628.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Titan Micro Electronics TM1628 LED controller
> +
> +maintainers:
> + - Andreas Färber <afaerber@suse.de>
> +
> +properties:
> + compatible:
> + enum:
> + - titanmec,tm1628
> +
> + reg:
> + maxItems: 1
> +
> + "#grids":
I'd be more a fan of using '#' prefix if we'd been better at using it
when appropriate, so I'd probably drop the '#'.
> + description: |
> + Number of GRID output lines to use.
> + This limits the number of available SEG output lines.
> + minimum: 4
> + maximum: 7
> +
> + "#address-cells":
> + const: 2
> +
> + "#size-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> +
> +patternProperties:
> + "^.*@[1-7],([1-9]|1[02-4])$":
> + type: object
> + description: |
> + Properties for a single LED.
Please describe the unit-address format. I assume it's <grid>,<segment>.
> +
> + properties:
> + reg:
> + description: |
> + 1-based grid number, followed by 1-based segment number.
> + maxItems: 1
> +
> + linux,default-trigger: true
> +
> + required:
> + - reg
> +
> +examples:
> + - |
> + #include <dt-bindings/leds/common.h>
> +
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + led-controller@0 {
> + compatible = "titanmec,tm1628";
> + reg = <0>;
> + spi-3-wire;
> + spi-lsb-first;
> + spi-max-frequency = <500000>;
> + #grids = <7>;
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + colon@5,4 {
> + reg = <5 4>;
> + color = <LED_COLOR_ID_WHITE>;
> + function = LED_FUNCTION_INDICATOR;
> + linux,default-trigger = "heartbeat";
> + };
> + };
> + };
> +...
> --
> 2.16.4
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-19 23:04 UTC|newest]
Thread overview: 132+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 3:39 [RFC 00/25] arm64: realtek: Add Xnano X5 and implement TM1628/FD628/AiP1618 LED controllers Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 01/25] dt-bindings: vendor-prefixes: Add Xnano Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 22:26 ` Rob Herring
2019-12-19 22:26 ` Rob Herring
2019-12-12 3:39 ` [RFC 02/25] dt-bindings: arm: realtek: Add Xnano X5 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 22:27 ` Rob Herring
2019-12-19 22:27 ` Rob Herring
2019-12-12 3:39 ` [RFC 03/25] arm64: dts: realtek: rtd1295: " Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 04/25] spi: gpio: Implement LSB First bitbang support Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 8:40 ` Geert Uytterhoeven
2019-12-12 8:40 ` Geert Uytterhoeven
2019-12-12 15:14 ` Andreas Färber
2019-12-12 15:14 ` Andreas Färber
2019-12-12 17:19 ` Mark Brown
2019-12-12 17:19 ` Mark Brown
2019-12-12 21:08 ` Andreas Färber
2019-12-12 21:08 ` Andreas Färber
2019-12-13 11:42 ` Mark Brown
2019-12-13 11:42 ` Mark Brown
2019-12-12 3:39 ` [RFC 05/25] dt-bindings: vendor-prefixes: Add Titan Micro Electronics Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 22:31 ` Rob Herring
2019-12-19 22:31 ` Rob Herring
2019-12-12 3:39 ` [RFC 06/25] dt-bindings: leds: Add Titan Micro Electronics TM1628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 23:04 ` Rob Herring [this message]
2019-12-19 23:04 ` Rob Herring
2019-12-12 3:39 ` [RFC 07/25] " Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-14 9:48 ` Andreas Färber
2019-12-14 9:48 ` Andreas Färber
2019-12-12 3:39 ` [RFC 08/25] arm64: dts: realtek: rtd129x-zidoo-x9s: Add TM1628 LED controller Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 09/25] arm64: dts: realtek: rtd1295-zidoo-x9s: Add regular LEDs to TM1628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 10/25] dt-bindings: vendor-prefixes: Add Fuda Hisi Microelectronics Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 23:04 ` Rob Herring
2019-12-19 23:04 ` Rob Herring
2019-12-12 3:39 ` [RFC 11/25] dt-bindings: leds: tm1628: Add Fuda Hisi Microelectronics FD628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 23:05 ` Rob Herring
2019-12-19 23:05 ` Rob Herring
2019-12-12 3:39 ` [RFC 12/25] " Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 13/25] arm64: dts: realtek: rtd1295-xnano-x5: Add FD628 LED controller Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 14/25] arm64: dts: realtek: rtd1295-xnano-x5: Add regular LEDs to FD628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-21 20:21 ` Pavel Machek
2019-12-21 20:21 ` Pavel Machek
2019-12-12 3:39 ` [RFC 15/25] dt-bindings: vendor-prefixes: Add Fude Microelectronics Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 23:05 ` Rob Herring
2019-12-19 23:05 ` Rob Herring
2019-12-12 3:39 ` [RFC 16/25] dt-bindings: leds: tm1628: Add Fude Microelectronics AiP1618 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-19 23:06 ` Rob Herring
2019-12-19 23:06 ` Rob Herring
2019-12-12 3:39 ` [RFC 17/25] leds: tm1628: Prepare " Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-21 19:55 ` Andreas Färber
2019-12-21 19:55 ` Andreas Färber
2019-12-12 3:39 ` [RFC 18/25] dt-bindings: leds: tm1628: Define display child nodes Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 19/25] leds: tm1628: Add 7-segment display support Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 8:33 ` Geert Uytterhoeven
2019-12-12 8:33 ` Geert Uytterhoeven
2019-12-12 14:10 ` Andreas Färber
2019-12-12 14:10 ` Andreas Färber
2019-12-21 20:23 ` Pavel Machek
2019-12-21 20:23 ` Pavel Machek
2019-12-12 3:39 ` [RFC 20/25] arm64: dts: realtek: rtd1295-zidoo-x9s: Add display to TM1628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 21/25] arm64: dts: realtek: rtd1295-xnano-x5: Add display to FD628 Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 22/25] leds: tm1826: Add combined glyph support Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-21 20:27 ` Pavel Machek
2019-12-21 20:27 ` Pavel Machek
2019-12-21 20:41 ` Andreas Färber
2019-12-21 20:41 ` Andreas Färber
2019-12-21 21:04 ` Pavel Machek
2019-12-21 21:04 ` Pavel Machek
2019-12-21 21:49 ` Andreas Färber
2019-12-21 21:49 ` Andreas Färber
[not found] ` <CANiq72nA9OLa0SjY8W055J_2A32tcp7S98SruKSdWH2dm25VKw@mail.gmail.com>
2019-12-22 3:14 ` Andreas Färber
2019-12-22 3:14 ` Andreas Färber
2020-01-15 14:31 ` Miguel Ojeda
2020-01-15 14:31 ` Miguel Ojeda
2019-12-12 3:39 ` [RFC 23/25] WIP: leds: tm1628: Prepare TM1628 keys Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 24/25] WIP: leds: tm1628: Prepare FD628 keys Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 3:39 ` [RFC 25/25] WIP: leds: tm1628: Prepare AiP1618 keys Andreas Färber
2019-12-12 3:39 ` Andreas Färber
2019-12-12 13:14 ` [RFC 00/25] arm64: realtek: Add Xnano X5 and implement TM1628/FD628/AiP1618 LED controllers Robin Murphy
2019-12-12 13:14 ` Robin Murphy
2019-12-12 13:14 ` Robin Murphy
2019-12-12 20:55 ` Andreas Färber
2019-12-12 20:55 ` Andreas Färber
2019-12-12 20:55 ` Andreas Färber
2019-12-13 14:07 ` Robin Murphy
2019-12-13 14:07 ` Robin Murphy
2019-12-13 14:07 ` Robin Murphy
2019-12-13 14:36 ` Geert Uytterhoeven
2019-12-13 14:36 ` Geert Uytterhoeven
2019-12-13 14:36 ` Geert Uytterhoeven
2020-02-25 21:42 ` Ezra Buehler
2020-02-25 21:42 ` Ezra Buehler
2020-02-25 21:42 ` Ezra Buehler
2020-02-26 13:03 ` Pavel Machek
2020-02-26 13:03 ` Pavel Machek
2020-02-26 13:03 ` Pavel Machek
2020-02-26 13:03 ` Pavel Machek
2019-12-21 18:20 ` Pavel Machek
2019-12-21 18:20 ` Pavel Machek
2019-12-21 18:20 ` Pavel Machek
2019-12-21 21:07 ` Andreas Färber
2019-12-21 21:07 ` Andreas Färber
2019-12-21 21:07 ` Andreas Färber
2020-01-15 13:34 ` Andreas Färber
2020-01-15 13:34 ` Andreas Färber
2020-01-15 13:34 ` Andreas Färber
2020-01-15 13:34 ` Andreas Färber
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=20191219230335.GA25461@bogus \
--to=robh@kernel.org \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=zypeng@titanmec.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.