From: Rob Herring <robh@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Andreas Färber" <afaerber@suse.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>
Subject: Re: [PATCH v3 2/5] dt-bindings: auxdisplay: Add Titan Micro Electronics TM1628
Date: Thu, 24 Feb 2022 14:22:39 -0600 [thread overview]
Message-ID: <YhfpD9qfcuAlC+wp@robh.at.kernel.org> (raw)
In-Reply-To: <2b7f0011-8872-70fa-b9b7-50b7817e7084@gmail.com>
On Wed, Feb 23, 2022 at 06:59:31PM +0100, Heiner Kallweit wrote:
> Add a YAML schema binding for TM1628 auxdisplay
> (7/11-segment LED) controller.
>
> This patch is partially based on previous work from
> Andreas Färber <afaerber@suse.de>.
>
> Co-Developed-by: Andreas Färber <afaerber@suse.de>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> Co-Developed-by: Heiner Kallweit <hkallweit1@gmail.com>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> v3:
> - fix remaining YAML issues
> - use Co-Developed-by
> ---
> .../bindings/auxdisplay/titanmec,tm1628.yaml | 92 +++++++++++++++++++
> 1 file changed, 92 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/auxdisplay/titanmec,tm1628.yaml
>
> diff --git a/Documentation/devicetree/bindings/auxdisplay/titanmec,tm1628.yaml b/Documentation/devicetree/bindings/auxdisplay/titanmec,tm1628.yaml
> new file mode 100644
> index 000000000..2a1ef692c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/auxdisplay/titanmec,tm1628.yaml
> @@ -0,0 +1,92 @@
> +# SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/auxdisplay/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>
> + - Heiner Kallweit <hkallweit1@gmail.com>
> +
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> +properties:
> + compatible:
> + const: titanmec,tm1628
> +
> + reg:
> + maxItems: 1
> +
> + grid:
> + description:
> + Mapping of display digit position to grid number.
> + This implicitly defines the display size.
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + minItems: 1
> + maxItems: 7
> +
> + segment-mapping:
> + description:
> + Mapping of 7 segment display segments A-G to bit numbers 1-12.
> + $ref: /schemas/types.yaml#/definitions/uint8-array
> + minItems: 7
> + maxItems: 7
Are these properties useful for any 7 segment display or specific to
this controller?
The commit msg mentions 11 segment display. Does this need to be?:
oneOf:
- minItems: 7
maxItems: 7
- minItems: 11
maxItems: 11
> +
> + "#address-cells":
> + const: 2
> +
> + "#size-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> +
> +patternProperties:
> + "^.*@[1-7],([1-9]|1[0-6])$":
> + type: object
> + $ref: /schemas/leds/common.yaml#
> + unevaluatedProperties: false
> + description: |
> + Properties for a single LED.
> +
> + properties:
> + reg:
> + description: |
> + 1-based grid number, followed by 1-based segment bit number.
> + maxItems: 1
> +
> + required:
> + - reg
> +
> +unevaluatedProperties: false
> +
> +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>;
> + grid = /bits/ 8 <4 3 2 1>;
> + segment-mapping = /bits/ 8 <4 5 6 1 2 3 7>;
> + #address-cells = <2>;
> + #size-cells = <0>;
> +
> + alarmn@5,4 {
> + reg = <5 4>;
> + function = LED_FUNCTION_ALARM;
> + };
> + };
> + };
> +...
> --
> 2.35.1
>
>
>
next prev parent reply other threads:[~2022-02-24 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 17:56 [PATCH v3 0/5] auxdisplay: Add support for the Titanmec TM1628 7 segment display controller Heiner Kallweit
2022-02-23 17:57 ` [PATCH v3 1/5] dt-bindings: vendor-prefixes: Add Titan Micro Electronics Heiner Kallweit
2022-02-23 17:59 ` [PATCH v3 2/5] dt-bindings: auxdisplay: Add Titan Micro Electronics TM1628 Heiner Kallweit
2022-02-24 20:22 ` Rob Herring [this message]
2022-02-24 20:55 ` Heiner Kallweit
2022-02-24 21:30 ` Rob Herring
2022-02-24 22:07 ` Heiner Kallweit
2022-02-23 18:00 ` [PATCH v3 3/5] docs: ABI: document tm1628 attribute display-text Heiner Kallweit
2022-02-23 18:01 ` [PATCH v3 4/5] auxdisplay: add support for Titanmec TM1628 7 segment display controller Heiner Kallweit
2022-02-23 20:28 ` Miguel Ojeda
2022-02-23 22:30 ` Heiner Kallweit
2022-02-23 18:02 ` [PATCH v3 5/5] arm64: dts: meson-gxl-s905w-tx3-mini: add support for the 7 segment display Heiner Kallweit
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=YhfpD9qfcuAlC+wp@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=ojeda@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).