From patchwork Sun Sep 8 21:07:54 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?q?Heiko_St=C3=BCbner?= X-Patchwork-Id: 13795618 Received: from gloria.sntech.de (gloria.sntech.de [185.11.138.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0D5C417BB21; Sun, 8 Sep 2024 21:09:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.11.138.130 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725829801; cv=none; b=jBR7XKSXoHzsriXMLMf1Saj5LkmLdNuhBzimFIMgo23PlF6RU/DFoNFcWQF/DqxalGtIUExjGdy+YOrrXWr60RYIg8rvNOyQ8AgW7WHWpE+5Wu/v0GkfEWP/GgcyrHLzUYSAhncRZhfC+c3py4gOGd+ggSqNsVjZe1zXQF3bHFU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1725829801; c=relaxed/simple; bh=4VXE2x4NSw8emUUpj3uJHU1W4cfHreQcCtdOxGuG5kU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=efF92IIc5/DClvCGFlqr0IKijzsu5fWMqh4jpPMDJyS5iwTsompXZ6aSuqgiNaP1pw+TRU+xXrBofc8ZJDS903h9s/Hg2T2rIXddsjtrwF1DG/FR7eM+ZBYg7hx5ZjlMZu/VzTTpNvjL4YOVIUyTFn6Bg0/wjGG6c0QafrxtfxU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sntech.de; spf=pass smtp.mailfrom=sntech.de; dkim=pass (2048-bit key) header.d=sntech.de header.i=@sntech.de header.b=nxes8+Mg; arc=none smtp.client-ip=185.11.138.130 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sntech.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sntech.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sntech.de header.i=@sntech.de header.b="nxes8+Mg" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sntech.de; s=gloria202408; h=Content-Transfer-Encoding:MIME-Version:Message-ID:Date: Subject:Cc:To:From:Sender:Reply-To:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=bJYmi9c9oz6tm2pyzXmgxUUZvpQmzK+TNH7qhaJHuP4=; b=nxes8+Mgd1KylK6uEjYsusu31I NX+wkjgMwadO2am6zoSRtvJtFs/e2I70OooJHgTIQCJc7Yfl5tgFVpoUslKegImmDcKAVvWT7i10Y 9nF0miCzg1xB+PlbrEHLPHp6sqxwhYRJY8oykOw3SHC5W9JuMQLIPyU6FIFeWD1ANAlSdbnX7lnu4 le4J30MmN0b8iWCS8P9kI+sLk0msBiHgwcSWnXTAW25ZKff6eQoMkbVLTb3uOR2s0djSN766CC5vT 5jWNstERwHC5CzBfAru+jRxMtNvlXN+T99G3xi7D5IJ6fh31i5Ap1iP2PJUstBsL4RIRHnZsYk1ss Wz6I04UQ==; Received: from i5e8616cc.versanet.de ([94.134.22.204] helo=phil.lan) by gloria.sntech.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1snPA0-0003s9-8T; Sun, 08 Sep 2024 23:09:28 +0200 From: Heiko Stuebner 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 Stuebner Subject: [PATCH v8 0/9] Drivers to support the MCU on QNAP NAS devices Date: Sun, 8 Sep 2024 23:07:54 +0200 Message-ID: <20240908210803.3339919-1-heiko@sntech.de> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-iio@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 This implements a set of drivers for the MCU used on QNAP NAS devices. Of course no documentation for the serial protocol is available, so thankfully QNAP has a tool on their rescue-inird to talk to the MCU and I found interceptty [0] to listen to what goes over the serial connection. In general it looks like there are two different generations in general, an "EC" device and now this "MCU" - referenced in the strings of the userspace handlers for those devices. For the MCU "SPEC3" and "SPEC4" are listed which is configured in the model.conf of the device. When setting the value from SPEC4 to SPEC3 on my TS433, the supported commands change, but the command interface stays the same and especially the version command is the same. The binding also does not expose any interals of the device that might change, so hopefully there shouldn't be big roadblocks to support different devices, apart from possibly adapting the commands. changes in v8: - patch for hid-sensor hub to not do wonky stuff with an old platform-data copy I hope my reading of the situation is correct here, but that initial platform_data really seemed wrong mfd: - flush serial before writing a new command - wait for send to complete before starting the receive wait-timeout - set expected length to 0 directly when the reply is complete not after leaving the receive callback changes in v7: - use ASCII representation in commands where possible instead of hex vals - drop get_variant function and use mfd platform-data instead mfd: - a lot of style improvements leds: - name variables better (value -> brightness, num -> num_err_led) - handle preservation of blink mode more effectively - snprintf -> scnprintf - drop duplicate "failed to register ... LED" messages changes in v6: - format mcu commands arrays in single lines (Lee) mfd: - drop obsolete remain kdoc for the removed reply_lock (kernel test robot) changes in v5: binding: - add Conor's Reviewed-by mfd: Address comments from Lee - improve commit message - improve Kconfig help text - sort headers alphabetical - style and spelling improvements - constants for magic numbers - drop reply assignment, the mcu only replies to commands sent to it, so there should only ever be one command in fligth. hwmon: Add Acked-by from Guenter and address some remarks - don't allow empty fan subnode - use num var directly when getting cooling levels, without using ret intermediate - use dev_err_probe in thermal init function changes in v4: binding: - move cooling properties into a fan subnode and reference fan-common.yaml (Rob) - dropped Krzysztof's Ack because of this mfd: - use correct format-string for size_t (kernel test robot) input: - added Dmitry's Ack hwmon: - adapted to fan-subnode when reading cooling properties - dropped Guenter's Ack because of this changes in v3: mfd - use correct power-off priority: default - constify the cmd-data array in command functions (Dmitry) leds: - don't point to temporary buffers for cdev->name (Florian Eckert) hwmon: - use clamp_val(), don't try to reimplement (Guenter) - add Guenter's Ack input: address Dmitry's comments - constify some cmd arrays - add input-close callback to cancel beep worker - drop initial input event report changes in v2: binding: - rename to qnap,ts433-mcu.yaml (Krzysztof) - drop "preserve formatting" indicator (Krzysztof) - add Krzysztof's Review tag mfd: - fix checkpatch --strict CHECKs - add a MAINTAINERS entry for all qnap-mcu-parts Heiko Stuebner (9): HID: hid-sensor-hub: don't use stale platform-data on remove mfd: core: make platform_data pointer const in struct mfd_cell dt-bindings: mfd: add binding for qnap,ts433-mcu devices mfd: add base driver for qnap-mcu devices leds: add driver for LEDs from qnap-mcu devices Input: add driver for the input part of qnap-mcu devices hwmon: add driver for the hwmon parts of qnap-mcu devices arm64: dts: rockchip: hook up the MCU on the QNAP TS433 arm64: dts: rockchip: set hdd led labels on qnap-ts433 .../bindings/mfd/qnap,ts433-mcu.yaml | 42 ++ Documentation/hwmon/index.rst | 1 + Documentation/hwmon/qnap-mcu-hwmon.rst | 27 ++ MAINTAINERS | 9 + .../boot/dts/rockchip/rk3568-qnap-ts433.dts | 61 +++ drivers/hid/hid-sensor-hub.c | 21 +- drivers/hwmon/Kconfig | 12 + drivers/hwmon/Makefile | 1 + drivers/hwmon/qnap-mcu-hwmon.c | 364 ++++++++++++++++++ drivers/input/misc/Kconfig | 12 + drivers/input/misc/Makefile | 1 + drivers/input/misc/qnap-mcu-input.c | 153 ++++++++ drivers/leds/Kconfig | 11 + drivers/leds/Makefile | 1 + drivers/leds/leds-qnap-mcu.c | 227 +++++++++++ drivers/mfd/Kconfig | 13 + drivers/mfd/Makefile | 2 + drivers/mfd/qnap-mcu.c | 332 ++++++++++++++++ include/linux/mfd/core.h | 2 +- include/linux/mfd/qnap-mcu.h | 26 ++ 20 files changed, 1310 insertions(+), 8 deletions(-) create mode 100644 Documentation/devicetree/bindings/mfd/qnap,ts433-mcu.yaml create mode 100644 Documentation/hwmon/qnap-mcu-hwmon.rst create mode 100644 drivers/hwmon/qnap-mcu-hwmon.c create mode 100644 drivers/input/misc/qnap-mcu-input.c create mode 100644 drivers/leds/leds-qnap-mcu.c create mode 100644 drivers/mfd/qnap-mcu.c create mode 100644 include/linux/mfd/qnap-mcu.h