From: Adam Baker <linux@baker-net.org.uk>
To: Manish Baing <manishbaing2789@gmail.com>,
linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: hwmon: zyxel,nsa320-mcu: convert to DT schema
Date: Fri, 1 May 2026 22:53:22 +0100 [thread overview]
Message-ID: <56d985c5-e795-4108-9045-c7b3ab8f71ae@baker-net.org.uk> (raw)
In-Reply-To: <20260501102116.8275-1-manishbaing2789@gmail.com>
Acked-By: Adam Baker <linux@baker-net.org.uk>
On 01/05/2026 11:21, Manish Baing wrote:
> Convert the ZyXEL NSA320 MCU bindings from text format to YAML schema.
>
> Signed-off-by: Manish Baing <manishbaing2789@gmail.com>
> ---
> .../devicetree/bindings/hwmon/nsa320-mcu.txt | 20 -------
> .../bindings/hwmon/zyxel,nsa320-mcu.yaml | 54 +++++++++++++++++++
> 2 files changed, 54 insertions(+), 20 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt
> create mode 100644 Documentation/devicetree/bindings/hwmon/zyxel,nsa320-mcu.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt b/Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt
> deleted file mode 100644
> index 0863e067c85b..000000000000
> --- a/Documentation/devicetree/bindings/hwmon/nsa320-mcu.txt
> +++ /dev/null
> @@ -1,20 +0,0 @@
> -Bindings for the fan / temperature monitor microcontroller used on
> -the Zyxel NSA 320 and several subsequent models.
> -
> -Required properties:
> -- compatible : "zyxel,nsa320-mcu"
> -- data-gpios : The GPIO pin connected to the data line on the MCU
> -- clk-gpios : The GPIO pin connected to the clock line on the MCU
> -- act-gpios : The GPIO pin connected to the active line on the MCU
> -
> -Example:
> -
> - hwmon {
> - compatible = "zyxel,nsa320-mcu";
> - pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act>;
> - pinctrl-names = "default";
> -
> - data-gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
> - clk-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
> - act-gpios = <&gpio0 17 GPIO_ACTIVE_LOW>;
> - };
> diff --git a/Documentation/devicetree/bindings/hwmon/zyxel,nsa320-mcu.yaml b/Documentation/devicetree/bindings/hwmon/zyxel,nsa320-mcu.yaml
> new file mode 100644
> index 000000000000..a111f8125e09
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/zyxel,nsa320-mcu.yaml
> @@ -0,0 +1,54 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwmon/zyxel,nsa320-mcu.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ZyXEL NSA320 MCU
> +
> +maintainers:
> + - Adam Baker <linux@baker-net.org.uk>
> + - Guenter Roeck <linux@roeck-us.net>
> +
> +description:
> + The ZyXEL NSA320 uses a dedicated microcontroller to manage system-critical
> + functions like fan speed and power monitoring. It is connected to the SoC
> + via a GPIO-based serial protocol.
> +
> +properties:
> + compatible:
> + const: zyxel,nsa320-mcu
> +
> + data-gpios:
> + maxItems: 1
> + description: GPIO pin connected to the data line on the MCU.
> +
> + clk-gpios:
> + maxItems: 1
> + description: GPIO pin connected to the clock line on the MCU.
> +
> + act-gpios:
> + maxItems: 1
> + description: GPIO pin connected to the active line on the MCU.
> +
> +required:
> + - compatible
> + - data-gpios
> + - clk-gpios
> + - act-gpios
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + hwmon {
> + compatible = "zyxel,nsa320-mcu";
> + pinctrl-0 = <&pmx_mcu_data &pmx_mcu_clk &pmx_mcu_act>;
> + pinctrl-names = "default";
> +
> + data-gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
> + clk-gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
> + act-gpios = <&gpio0 17 GPIO_ACTIVE_LOW>;
> + };
next prev parent reply other threads:[~2026-05-01 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 10:21 [PATCH] dt-bindings: hwmon: zyxel,nsa320-mcu: convert to DT schema Manish Baing
2026-05-01 21:53 ` Adam Baker [this message]
2026-05-04 10:29 ` Krzysztof Kozlowski
2026-05-04 10:30 ` Krzysztof Kozlowski
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=56d985c5-e795-4108-9045-c7b3ab8f71ae@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=manishbaing2789@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