From: "Jean-François Lessard" <jefflessard3@gmail.com>
To: Andy Shevchenko <andy@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
devicetree@vger.kernel.org, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
"Boris Gjenero" <boris.gjenero@gmail.com>,
"Christian Hewitt" <christianshewitt@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Paolo Sabatino" <paolo.sabatino@gmail.com>
Subject: [PATCH v2 6/8] dt-bindings: auxdisplay: add Titan Micro Electronics TM16XX
Date: Sun, 29 Jun 2025 08:59:56 -0400 [thread overview]
Message-ID: <20250629130002.49842-8-jefflessard3@gmail.com> (raw)
In-Reply-To: <20250629130002.49842-1-jefflessard3@gmail.com>
Add documentation for Titanmec TM16XX and compatible LED display controllers.
This patch is inspired by previous work from Andreas Färber and Heiner Kallweit.
Co-developed-by: Andreas Färber <afaerber@suse.de>
Co-developed-by: Heiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: Jean-François Lessard <jefflessard3@gmail.com>
---
.../bindings/auxdisplay/titanmec,tm16xx.yaml | 210 ++++++++++++++++++
1 file changed, 210 insertions(+)
create mode 100644 Documentation/devicetree/bindings/auxdisplay/titanmec,tm16xx.yaml
diff --git a/Documentation/devicetree/bindings/auxdisplay/titanmec,tm16xx.yaml b/Documentation/devicetree/bindings/auxdisplay/titanmec,tm16xx.yaml
new file mode 100644
index 0000000000..65c43e3ba4
--- /dev/null
+++ b/Documentation/devicetree/bindings/auxdisplay/titanmec,tm16xx.yaml
@@ -0,0 +1,210 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/auxdisplay/titanmec,tm16xx.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Auxiliary displays based on TM16xx and compatible LED controllers
+
+maintainers:
+ - Jean-François Lessard <jefflessard3@gmail.com>
+
+description: |
+ TM16xx controllers manage a matrix of LEDs organized in grids (rows) and segments (columns).
+ Each grid or segment can be wired to drive either a digit or individual icons, depending on the
+ board design.
+
+ Typical display example:
+
+ --- --- --- ---
+ WIFI | | | | - | | | | USB PLAY
+ --- --- --- ---
+ LAN | | | | - | | | | BT PAUSE
+ --- --- --- ---
+
+ The controller itself is agnostic of the display layout. The specific arrangement
+ (which grids and segments drive which digits or icons) is determined by the board-level
+ wiring. Therefore, these bindings describe hardware configuration at the PCB level
+ to enable support of multiple display implementations using these LED controllers.
+
+properties:
+ compatible:
+ enum:
+ - titanmec,tm1618
+ - titanmec,tm1620
+ - titanmec,tm1628
+ - titanmec,tm1650
+ - fdhisi,fd620
+ - fdhisi,fd628
+ - fdhisi,fd650
+ - fdhisi,fd6551
+ - fdhisi,fd655
+ - icore,aip650
+ - icore,aip1618
+ - icore,aip1628
+ - princeton,pt6964
+ - winrise,hbs658
+
+ reg:
+ maxItems: 1
+
+ titanmec,digits:
+ description: |
+ Array of grid (row) indexes corresponding to specific wiring of digits in the display matrix.
+ Defines which grid lines are connected to digit elements.
+ $ref: /schemas/types.yaml#/definitions/uint8-array
+ items:
+ minimum: 0
+ maximum: 7
+ minItems: 1
+ maxItems: 8
+
+ titanmec,segment-mapping:
+ description: |
+ Array of segment (column) indexes specifying the hardware layout mapping used for digit display.
+ Each entry gives the segment index corresponding to a standard 7-segment element (a-g).
+ $ref: /schemas/types.yaml#/definitions/uint8-array
+ items:
+ minimum: 0
+ maximum: 7
+ minItems: 7
+ maxItems: 7
+
+ titanmec,transposed:
+ description: |
+ Optional flag indicating if grids and segments are swapped compared to standard matrix orientation.
+ This accommodates devices where segments are wired to rows and grids to columns.
+ $ref: /schemas/types.yaml#/definitions/flag
+
+ "#address-cells":
+ const: 2
+
+ "#size-cells":
+ const: 0
+
+patternProperties:
+ "^led@[0-7],[0-7]$":
+ $ref: /schemas/leds/common.yaml#
+ properties:
+ reg:
+ description: Grid (row) and segment (column) index in the matrix of this individual LED icon
+ required:
+ - reg
+
+required:
+ - compatible
+ - reg
+ - titanmec,digits
+ - titanmec,segment-mapping
+
+additionalProperties: true
+
+examples:
+ - |
+ #include <dt-bindings/leds/common.h>
+
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ display-controller@24 {
+ reg = <0x24>;
+ compatible = "fdhisi,fd655";
+ titanmec,digits = [01 02 03 04];
+ titanmec,segment-mapping = [03 04 05 00 01 02 06];
+ #address-cells = <2>;
+ #size-cells = <0>;
+
+ led@0,0 {
+ reg = <0 0>;
+ function = LED_FUNCTION_ALARM;
+ };
+
+ led@0,1 {
+ reg = <0 1>;
+ function = LED_FUNCTION_USB;
+ };
+
+ led@0,2 {
+ reg = <0 2>;
+ function = "play";
+ };
+
+ led@0,3 {
+ reg = <0 3>;
+ function = "pause";
+ };
+
+ led@0,4 {
+ reg = <0 4>;
+ function = "colon";
+ };
+
+ led@0,5 {
+ reg = <0 5>;
+ function = LED_FUNCTION_LAN;
+ };
+
+ led@0,6 {
+ reg = <0 6>;
+ function = LED_FUNCTION_WLAN;
+ };
+ };
+ };
+
+ - |
+ #include <dt-bindings/leds/common.h>
+
+ spi {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ display-controller@0 {
+ reg = <0x0>;
+ compatible = "fdhisi,fd628";
+ titanmec,transposed;
+ titanmec,digits = [00 01 02 03];
+ titanmec,segment-mapping = [00 01 02 03 04 05 06];
+ spi-3wire;
+ spi-lsb-first;
+ spi-rx-delay-us = <1>;
+ spi-max-frequency = <500000>;
+ #address-cells = <2>;
+ #size-cells = <0>;
+
+ led@4,0 {
+ reg = <4 0>;
+ function = "apps";
+ };
+
+ led@4,1 {
+ reg = <4 1>;
+ function = "setup";
+ };
+
+ led@4,2 {
+ reg = <4 2>;
+ function = LED_FUNCTION_USB;
+ };
+
+ led@4,3 {
+ reg = <4 3>;
+ function = LED_FUNCTION_SD;
+ };
+
+ led@4,4 {
+ reg = <4 4>;
+ function = "colon";
+ };
+
+ led@4,5 {
+ reg = <4 5>;
+ function = "hdmi";
+ };
+
+ led@4,6 {
+ reg = <4 6>;
+ function = "video";
+ };
+ };
+ };
--
2.43.0
next prev parent reply other threads:[~2025-06-29 13:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 12:59 [PATCH v2 0/8] auxdisplay: Add TM16xx and compatible LED display controllers driver Jean-François Lessard
2025-06-29 12:59 ` Jean-François Lessard
2025-06-29 12:59 ` [PATCH v2 1/8] dt-bindings: vendor-prefixes: Add Fuda Hisi Microelectronics Jean-François Lessard
2025-06-29 12:59 ` [PATCH v2 2/8] dt-bindings: vendor-prefixes: Add Titan Micro Electronics Jean-François Lessard
2025-06-29 12:59 ` [PATCH v2 3/8] dt-bindings: vendor-prefixes: Add Princeton Technology Corp Jean-François Lessard
2025-07-03 7:32 ` Krzysztof Kozlowski
2025-07-03 8:13 ` Geert Uytterhoeven
2025-06-29 12:59 ` [PATCH v2 4/8] dt-bindings: vendor-prefixes: Add Winrise Technology Jean-François Lessard
2025-06-30 12:25 ` Krzysztof Kozlowski
2025-06-30 13:51 ` Christian Hewitt
2025-07-02 20:14 ` Krzysztof Kozlowski
2025-07-03 0:50 ` Jean-François Lessard
2025-06-29 12:59 ` [PATCH v2 5/8] dt-bindings: vendor-prefixes: Add Wuxi i-Core Electronics Jean-François Lessard
2025-06-30 6:07 ` Krzysztof Kozlowski
2025-06-30 8:19 ` Geert Uytterhoeven
2025-06-30 8:31 ` Christian Hewitt
2025-06-30 8:38 ` Geert Uytterhoeven
2025-06-30 12:24 ` Krzysztof Kozlowski
2025-06-30 13:53 ` Christian Hewitt
2025-06-29 12:59 ` Jean-François Lessard [this message]
2025-06-30 6:19 ` [PATCH v2 6/8] dt-bindings: auxdisplay: add Titan Micro Electronics TM16XX Krzysztof Kozlowski
2025-07-01 3:22 ` Jean-François Lessard
2025-07-02 15:02 ` Krzysztof Kozlowski
2025-07-02 15:07 ` Krzysztof Kozlowski
2025-07-02 17:30 ` Jean-François Lessard
2025-07-03 0:33 ` Jean-François Lessard
2025-07-03 7:33 ` Krzysztof Kozlowski
2025-06-29 13:18 ` [PATCH v2 7/8] auxdisplay: Add Titanmec TM16xx 7-segment display controllers driver Jean-François Lessard
2025-06-30 6:12 ` Krzysztof Kozlowski
2025-06-30 7:27 ` Andy Shevchenko
2025-06-30 9:27 ` Krzysztof Kozlowski
2025-06-30 9:54 ` Andy Shevchenko
2025-06-30 11:39 ` Krzysztof Kozlowski
2025-06-30 14:17 ` Andy Shevchenko
2025-07-02 15:05 ` Krzysztof Kozlowski
2025-07-02 15:19 ` Andy Shevchenko
2025-07-03 20:49 ` Miguel Ojeda
2025-07-04 8:23 ` Krzysztof Kozlowski
2025-07-04 9:26 ` Miguel Ojeda
2025-07-01 1:02 ` Jean-François Lessard
2025-07-01 1:32 ` kernel test robot
2025-06-29 13:19 ` [PATCH v2 8/8] MAINTAINERS: Add entry for TM16xx driver Jean-François Lessard
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=20250629130002.49842-8-jefflessard3@gmail.com \
--to=jefflessard3@gmail.com \
--cc=afaerber@suse.de \
--cc=andy@kernel.org \
--cc=boris.gjenero@gmail.com \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=paolo.sabatino@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).