From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 07775CC6B19 for ; Tue, 13 Oct 2026 16:30:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=bCylcL8r7dne6e2xSUn57/ruC99iqBkZb4CHlqtT1Rk=; b=W2/0FBeZjuO3jFg6OC6BTKYLLC Luoi4dBc80JwGNDBePtDqqPJC8v8SB47YyEHfnOiVjrBg2liA4ZhL7woSBvXbNiJoZGeLT9XSUrUA G8krr9SdmuG4jKzc5VeOLtFptHDFO2S/PHrtUQ0QGdHM54xQi2MbKxu0mDyGoS5YSCjWfNRQ5qsBE U7UfzFxRv1tdyOpS60Y5bZN4kkp4LMA4vaTMe2T162Pyh+u6Z1r0GL11LxhUthgv3qjj4ZNLVm6m9 TX2094xz6XSeIyTt66QXXBs6bz+C9Qrv3Wc/ozuIk0OEVXAPeFiklcC+raUzNPw4iTdaPF2nAWUbu ANzuLIfA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGfOe-0000000DVzF-2j1l; Tue, 13 Oct 2026 16:30:36 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGfOd-0000000DVyw-3Zsn for linux-arm-kernel@lists.infradead.org; Tue, 13 Oct 2026 16:30:35 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 00060602C3; Tue, 13 Oct 2026 16:30:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AC32D1F000FF; Tue, 13 Oct 2026 16:30:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791909034; bh=bCylcL8r7dne6e2xSUn57/ruC99iqBkZb4CHlqtT1Rk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ICic/5CHydH+9bIuXE2dag452kYIQD66ar9sDhSFziK7acorOlC2b8bwaJpcjdLTk pSO4dM9E8PXgsVbA7+4jpxZEeBlys/BOwQcPXPSUg+iSiZY5PGOC+qJMAjAfqZOMJt KuGn5E/rxXhExFAlde+eF/DzjYHZU7ZQ2cHI7KNz5myUOXQwYxqk6FJTZgXyvVWxHG nzFDLKHSya7+8Gic0X7znR/feoR8oTgrgYnZqwkmlFr1hT8i+vPr7u2XYmm0mcjO+r gCTLi2MehvMBJs2UkLM58h7ogPS7qWiQ5lNbm77jBCkaYLHDqRf+MGLDH/gsOjXr/y kbiwEoTzXL8vQ== Date: Tue, 13 Oct 2026 17:30:29 +0100 From: Conor Dooley To: Robert Marko Cc: linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, Steen.Hegelund@microchip.com, daniel.machon@microchip.com, UNGLinuxDriver@microchip.com, nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev, lars.povlsen@microchip.com, linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, luka.perkov@sartura.hr Subject: Re: [PATCH 1/6] dt-bindings: hwmon: sparx5: add LAN969x fan controller Message-ID: <20261013-stylized-plethora-2a9e27545adb@spud> References: <20261013125735.1542349-1-robert.marko@sartura.hr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XdQaVzIG9Y1sxA5J" Content-Disposition: inline In-Reply-To: <20261013125735.1542349-1-robert.marko@sartura.hr> X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --XdQaVzIG9Y1sxA5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 13, 2026 at 02:56:25PM +0200, Robert Marko wrote: > LAN969x integrates a PWM fan controller with a tachometer input in > addition to the Sparx5-compatible temperature sensor. Add a LAN969x > hardware-monitor compatible and describe the second register region. >=20 > Describe the fan as a child node using a two-cell PWM specifier for the > period and standard polarity flags. The child also carries the optional > tachometer pulses-per-revolution and thermal cooling properties. >=20 > Keep the existing microchip,lan9691-temp compatible for device tree ABI > compatibility. >=20 > Signed-off-by: Robert Marko > --- > .../bindings/hwmon/microchip,sparx5-temp.yaml | 90 ++++++++++++++++++- > 1 file changed, 87 insertions(+), 3 deletions(-) >=20 > diff --git a/Documentation/devicetree/bindings/hwmon/microchip,sparx5-tem= p.yaml b/Documentation/devicetree/bindings/hwmon/microchip,sparx5-temp.yaml > index 611fcadb1e771..e91c2a3ccd3c9 100644 > --- a/Documentation/devicetree/bindings/hwmon/microchip,sparx5-temp.yaml > +++ b/Documentation/devicetree/bindings/hwmon/microchip,sparx5-temp.yaml > @@ -4,13 +4,15 @@ > $id: http://devicetree.org/schemas/hwmon/microchip,sparx5-temp.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > =20 > -title: Microchip Sparx5 Temperature Monitor > +title: Microchip Sparx5 Hardware Monitor > =20 > maintainers: > - Lars Povlsen > =20 > description: | > - Microchip Sparx5 embedded temperature monitor > + Microchip Sparx5 temperature monitor with a fan controller on LAN969x. > + The fan child's pwms property references this node to specify the > + PWM period and polarity. > =20 > properties: > compatible: > @@ -18,11 +20,19 @@ properties: > - const: microchip,sparx5-temp > - items: > - enum: > + - microchip,lan9691-hwmon > - microchip,lan9691-temp > - const: microchip,sparx5-temp > =20 > reg: > - maxItems: 1 > + minItems: 1 > + maxItems: 2 > + > + reg-names: > + minItems: 1 > + items: > + - const: temp > + - const: fan > =20 > clocks: > items: > @@ -31,11 +41,67 @@ properties: > '#thermal-sensor-cells': > const: 0 > =20 > + '#pwm-cells': > + const: 2 > + description: | > + Number of cells in a PWM specifier. > + - cell 0: PWM period in nanoseconds > + - cell 1: PWM polarity: 0 or PWM_POLARITY_INVERTED > + > + fan: > + $ref: fan-common.yaml# > + unevaluatedProperties: false > + > + properties: > + cooling-levels: > + description: > + PWM duty-cycle values corresponding to thermal cooling states. > + items: > + maximum: 255 > + > + pulses-per-revolution: > + minimum: 1 > + maximum: 4 > + default: 2 > + > + required: > + - pwms > + > + dependencies: > + '#cooling-cells': > + - cooling-levels > + cooling-levels: > + - '#cooling-cells' > + > required: > - compatible > - reg > - clocks > =20 > +allOf: > + - if: > + properties: > + compatible: > + contains: > + const: microchip,lan9691-hwmon > + then: > + properties: > + reg: > + minItems: 2 > + reg-names: > + minItems: 2 > + required: > + - '#pwm-cells' > + - reg-names > + else: > + properties: > + '#pwm-cells': false > + fan: false > + reg: > + maxItems: 1 > + reg-names: > + maxItems: 1 > + > additionalProperties: false > =20 > examples: > @@ -46,3 +112,21 @@ examples: > #thermal-sensor-cells =3D <0>; > clocks =3D <&sys_clk>; > }; > + > + - | > + #include > + > + hwmon: hwmon@e2020100 { > + compatible =3D "microchip,lan9691-hwmon", "microchip,sparx5-temp= "; > + reg =3D <0xe2020100 0xc>, <0xe2010348 0xc>; Are these actually the same device? These are somewhat disparate register regions - and the second is at a very odd offset. Thanks, Conor. > + reg-names =3D "temp", "fan"; > + #pwm-cells =3D <2>; > + #thermal-sensor-cells =3D <0>; > + clocks =3D <&sys_clk>; > + > + fan { > + pwms =3D <&hwmon 40000 PWM_POLARITY_INVERTED>; > + cooling-levels =3D <0 128 192 255>; > + #cooling-cells =3D <2>; > + }; > + }; > --=20 > 2.56.0 >=20 --XdQaVzIG9Y1sxA5J Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCas5cpQAKCRB4tDGHoIJi 0lm9AQCXQpPsK/Qh9JeeV83vBvj/4SlEGRYK70WcyV1ZZ+XUbwD/RVsReE5mgon+ LvkceSyYW2eJr5Na+TSfbgUhFxZFYg4= =b6zh -----END PGP SIGNATURE----- --XdQaVzIG9Y1sxA5J--