linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: lee@kernel.org, jdelvare@suse.com, linux@roeck-us.net,
	dmitry.torokhov@gmail.com, pavel@ucw.cz, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, ukleinek@debian.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-hwmon@vger.kernel.org,
	linux-input@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 1/7] dt-bindings: mfd: add binding for qnap,ts433-mcu devices
Date: Mon, 12 Aug 2024 17:11:14 +0100	[thread overview]
Message-ID: <20240812-unlisted-cussed-ffa50b07a82d@spud> (raw)
In-Reply-To: <20240810184743.277248-2-heiko@sntech.de>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Sat, Aug 10, 2024 at 08:47:37PM +0200, Heiko Stuebner wrote:
> 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.
> 
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-08-12 16:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10 18:47 [PATCH v4 0/7] Drivers to support the MCU on QNAP NAS devices Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 1/7] dt-bindings: mfd: add binding for qnap,ts433-mcu devices Heiko Stuebner
2024-08-12 16:11   ` Conor Dooley [this message]
2024-08-10 18:47 ` [PATCH v4 2/7] mfd: add base driver for qnap-mcu devices Heiko Stuebner
2024-08-16 17:13   ` Lee Jones
2024-08-18 21:15     ` Heiko Stübner
2024-08-22 10:10       ` Lee Jones
2024-08-10 18:47 ` [PATCH v4 3/7] leds: add driver for LEDs from " Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 4/7] Input: add driver for the input part of " Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 5/7] hwmon: add driver for the hwmon parts " Heiko Stuebner
2024-08-13 16:03   ` Guenter Roeck
2024-08-13 20:39     ` Heiko Stübner
2024-08-10 18:47 ` [PATCH v4 6/7] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Heiko Stuebner
2024-08-10 18:47 ` [PATCH v4 7/7] arm64: dts: rockchip: set hdd led labels on qnap-ts433 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=20240812-unlisted-cussed-ffa50b07a82d@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=heiko@sntech.de \
    --cc=jdelvare@suse.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-hwmon@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=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;
as well as URLs for NNTP newsgroup(s).