From: Heiko Stuebner <heiko@sntech.de>
To: lee@kernel.org, jikos@kernel.org, jic23@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jdelvare@suse.com, linux@roeck-us.net,
srinivas.pandruvada@linux.intel.com, bentiss@kernel.org,
dmitry.torokhov@gmail.com, pavel@ucw.cz, ukleinek@debian.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-input@vger.kernel.org,
linux-iio@vger.kernel.org, linux-leds@vger.kernel.org,
heiko@sntech.de, Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v9 3/9] dt-bindings: mfd: add binding for qnap,ts433-mcu devices
Date: Thu, 7 Nov 2024 12:47:06 +0100 [thread overview]
Message-ID: <20241107114712.538976-4-heiko@sntech.de> (raw)
In-Reply-To: <20241107114712.538976-1-heiko@sntech.de>
These MCUs can be found in network attached storage devices made by QNAP.
They are connected to a serial port of the host device and provide
functionality like LEDs, power-control and temperature monitoring.
LEDs, buttons, etc are all elements of the MCU firmware itself, so don't
need devicetree input, though the fan gets its cooling settings from
a fan-0 subnode.
A binding for the LEDs for setting the linux-default-trigger may come
later, once all the LEDs are understood and ATA controllers actually
can address individual port-LEDs, but are really optional.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
---
.../bindings/mfd/qnap,ts433-mcu.yaml | 42 +++++++++++++++++++
1 file changed, 42 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml
diff --git a/Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml b/Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml
new file mode 100644
index 000000000000..877078ac172f
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml
@@ -0,0 +1,42 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mfd/qnap,ts433-mcu.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: QNAP NAS on-board Microcontroller
+
+maintainers:
+ - Heiko Stuebner <heiko@sntech.de>
+
+description:
+ QNAP embeds a microcontroller on their NAS devices adding system feature
+ as PWM Fan control, additional LEDs, power button status and more.
+
+properties:
+ compatible:
+ enum:
+ - qnap,ts433-mcu
+
+patternProperties:
+ "^fan-[0-9]+$":
+ $ref: /schemas/hwmon/fan-common.yaml#
+ unevaluatedProperties: false
+
+required:
+ - compatible
+
+additionalProperties: false
+
+examples:
+ - |
+ uart {
+ mcu {
+ compatible = "qnap,ts433-mcu";
+
+ fan-0 {
+ #cooling-cells = <2>;
+ cooling-levels = <0 64 89 128 166 204 221 238>;
+ };
+ };
+ };
--
2.45.2
next prev parent reply other threads:[~2024-11-07 11:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:47 [PATCH v9 0/9] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
2024-11-07 11:47 ` [PATCH v9 1/9] HID: hid-sensor-hub: don't use stale platform-data on remove Heiko Stuebner
2024-11-07 12:59 ` Jiri Kosina
2024-11-07 13:50 ` Heiko Stübner
2024-11-07 14:34 ` Jiri Kosina
2024-11-12 14:37 ` Lee Jones
2024-12-11 12:17 ` Lee Jones
2024-12-11 12:24 ` Jiri Kosina
2024-12-11 13:01 ` Heiko Stübner
2024-12-11 13:11 ` Jiri Kosina
2024-12-12 15:55 ` Lee Jones
2024-12-11 14:23 ` srinivas pandruvada
2024-11-07 11:47 ` [PATCH v9 2/9] mfd: core: make platform_data pointer const in struct mfd_cell Heiko Stuebner
2024-11-07 11:47 ` Heiko Stuebner [this message]
2024-11-07 11:47 ` [PATCH v9 4/9] mfd: add base driver for qnap-mcu devices Heiko Stuebner
2024-12-19 19:18 ` Kees Bakker
2024-12-19 19:43 ` Heiko Stübner
2024-12-19 19:51 ` Kees Bakker
2024-12-19 20:01 ` Heiko Stübner
2024-11-07 11:47 ` [PATCH v9 5/9] leds: add driver for LEDs from " Heiko Stuebner
2024-11-07 11:47 ` [PATCH v9 6/9] Input: add driver for the input part of " Heiko Stuebner
2024-11-07 11:47 ` [PATCH v9 7/9] hwmon: add driver for the hwmon parts " Heiko Stuebner
2024-11-07 11:47 ` [PATCH v9 8/9] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Heiko Stuebner
2024-11-07 11:47 ` [PATCH v9 9/9] arm64: dts: rockchip: set hdd led labels on qnap-ts433 Heiko Stuebner
2024-12-12 17:17 ` [PATCH v9 0/9] Drivers to support the MCU on QNAP NAS devices Lee Jones
2024-12-12 17:19 ` Lee Jones
2024-12-12 17:19 ` Lee Jones
2024-12-18 22:49 ` Heiko Stübner
2024-12-17 13:16 ` [GIT PULL] Immutable branch between MFD, HID, HWMON, Input and LEDs due for the v6.14 merge window Lee Jones
2024-12-18 21:06 ` (subset) [PATCH v9 0/9] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
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=20241107114712.538976-4-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=bentiss@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=ukleinek@debian.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