From nobody Sun Nov 24 05:36:48 2024 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 982932076A5; Thu, 7 Nov 2024 11:47:56 +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=1730980078; cv=none; b=oe/Xc/6k5pv0PQPuY/lYrp5cxfOdQ/l01p/c3JzJA8x6GVcTuSYcyAm9uHWeKdle75UbfvwpS8DyXhUpovngE0JuTAV5Nz466/HZQTWhtUO4vGL2xsdcfKTJjoy4QSFNk5acaF9gCtbEqrqGjzUR2XgXNEijL78vYKxMWLOU3PM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730980078; c=relaxed/simple; bh=7V9z8GpWh1h6jYTQK49Y2gITucVXURl5E73JrDwS5bk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=qvv3PAJDwGztCuarCXKW7R7SR6/UKqttgadAY1sENCL4jazGRY5DtQV+zMeSd1jtSizvKftuIit0qP5v4sBZyFI9P0M0IXqkBtKfmw2HRrFoXiksu+Z7fATuqYrM68s8iIfqpHdB7hyAPJs6wiwXeFP3fDNxElRMPpOrOEDgZwg= 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=POjBss8m; 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="POjBss8m" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sntech.de; s=gloria202408; h=Content-Transfer-Encoding:MIME-Version:References: In-Reply-To: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:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ndhE9GV/weSv1b+P8Z17HWDaizYEypq9zFWjTm9iZPo=; b=POjBss8m/sLHoH+2OuxfvWQqsK 8FN+lz93gu8/NZcpt7+vKhLZNYTLNSxKWBT89OiNlQy5MnqzBV2ld1O+3IO/O/vbqb2m/hvEWL+3+ 3TQfzvwKUalwksU9rXJPCkkJe9So1y3HFZNsPYSPs1eyeDmtZ5V+hIHyCjLhR8EidXwnibaSY/NFe 1KMceGJ/zRT9OWQNmzCak5EmXdWoNWh9x4TNUkcciaOkk9VvA4dLHd4azapZqAYcZUUW7auU7QV+x WzBMONwGjp6AchpiCILskqyKLvFGH5VM6JTw/yTdLm41KyMBxRjaVMJXV7ooEUzDAuQwkKwazAW4E Wyc0RMzQ==; Received: from i53875b28.versanet.de ([83.135.91.40] helo=localhost.localdomain) by gloria.sntech.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t90z4-0005lF-In; Thu, 07 Nov 2024 12:47:30 +0100 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@sntech.de Subject: [PATCH v9 8/9] arm64: dts: rockchip: hook up the MCU on the QNAP TS433 Date: Thu, 7 Nov 2024 12:47:11 +0100 Message-ID: <20241107114712.538976-9-heiko@sntech.de> X-Mailer: git-send-email 2.45.2 In-Reply-To: <20241107114712.538976-1-heiko@sntech.de> References: <20241107114712.538976-1-heiko@sntech.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" The MCU is an important part of the device functionality. It provides functionality like fan-control, more leds, etc and even more important without it, the NAS-device cannot even fully turned off. Hook up the serial device to its uart and hook into the thermal management to control the fan according to the cpu temperature. While the MCU also provides a temperature sensor for the case, this one is just polled and does not provide functionality for handling trip points in hardware, so a lot of polling would be involved. As the cpu is only cooled passively in these devices, it's temperature rising will indicate the temperature level of the system just earlier. Signed-off-by: Heiko Stuebner --- .../boot/dts/rockchip/rk3568-qnap-ts433.dts | 57 +++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/arch/arm64/boot/dts/rockchip/rk3568-qnap-ts433.dts b/arch/arm6= 4/boot/dts/rockchip/rk3568-qnap-ts433.dts index e601d9271ba8..4bc5f5691d45 100644 --- a/arch/arm64/boot/dts/rockchip/rk3568-qnap-ts433.dts +++ b/arch/arm64/boot/dts/rockchip/rk3568-qnap-ts433.dts @@ -483,6 +483,54 @@ rgmii_phy0: ethernet-phy@0 { }; }; =20 +/* + * The MCU can provide system temperature too, but only by polling and of + * course also cannot set trip points. So attach to the cpu thermal-zone + * instead to control the fan. + */ +&cpu_thermal { + trips { + case_fan0: case-fan0 { + hysteresis =3D <2000>; + temperature =3D <35000>; + type =3D "active"; + }; + + case_fan1: case-fan1 { + hysteresis =3D <2000>; + temperature =3D <45000>; + type =3D "active"; + }; + + case_fan2: case-fan2 { + hysteresis =3D <2000>; + temperature =3D <65000>; + type =3D "active"; + }; + }; + + cooling-maps { + /* + * Always provide some air movement, due to small case + * full of harddrives. + */ + map1 { + cooling-device =3D <&fan THERMAL_NO_LIMIT 1>; + trip =3D <&case_fan0>; + }; + + map2 { + cooling-device =3D <&fan 2 3>; + trip =3D <&case_fan1>; + }; + + map3 { + cooling-device =3D <&fan 4 THERMAL_NO_LIMIT>; + trip =3D <&case_fan2>; + }; + }; +}; + &pcie30phy { data-lanes =3D <1 2>; status =3D "okay"; @@ -582,6 +630,15 @@ &tsadc { */ &uart0 { status =3D "okay"; + + mcu { + compatible =3D "qnap,ts433-mcu"; + + fan: fan-0 { + #cooling-cells =3D <2>; + cooling-levels =3D <0 64 89 128 166 204 221 238>; + }; + }; }; =20 /* --=20 2.45.2