From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Potin Lai <potin.lai.pt@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Patrick Williams <patrick@stwcx.xyz>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Cosmo Chou <cosmo.chou@quantatw.com>,
Potin Lai <potin.lai@quantatw.com>
Subject: Re: [PATCH v5 05/10] ARM: dts: aspeed: catalina: Add second source fan controller support
Date: Fri, 21 Mar 2025 11:47:22 +1030 [thread overview]
Message-ID: <26a1d17c47c5ca6036dd58ac3b953daeec9f5ef8.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250320-potin-catalina-dts-update-20250102-v5-5-e161be6583a7@gmail.com>
Hi Potin,
On Thu, 2025-03-20 at 23:21 +0800, Potin Lai wrote:
> Add device tree nodes for the NCT7363 fan controllers on the second-
> source
> Power Distribution Board (PDB).
>
> Signed-off-by: Potin Lai <potin.lai.pt@gmail.com>
> ---
> .../dts/aspeed/aspeed-bmc-facebook-catalina.dts | 76
> ++++++++++++++++++++++
> 1 file changed, 76 insertions(+)
>
> diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-
> catalina.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-
> catalina.dts
> index fd22add90449..9cbb296dcd9e 100644
> --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dts
> +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-catalina.dts
> @@ -467,6 +467,82 @@ i2c1mux0ch2: i2c@2 {
> #size-cells = <0>;
> reg = <0x2>;
>
> + hwmon0: hwmon@1 {
There might be instances of calling nodes and labels 'hwmon' in other
(BMC) devicetrees, but I don't think we should continue that practice.
I think in this case it should be 'fan-controller'.
hwmon is the name of a kernel subsystem, not a class of hardware. The
devicetrees should describe the hardware (and not concepts from the
kernel).
> + compatible = "nuvoton,nct7363";
> + reg = <0x01>;
> + #pwm-cells = <2>;
> +
> + fan-9 {
> + pwms = <&hwmon0 0 40000>;
> + tach-ch = /bits/ 8 <0x09>;
> + };
> + fan-11 {
> + pwms = <&hwmon0 0 40000>;
> + tach-ch = /bits/ 8 <0x0b>;
> + };
> + fan-10 {
> + pwms = <&hwmon0 4 40000>;
> + tach-ch = /bits/ 8 <0x0a>;
> + };
> + fan-13 {
> + pwms = <&hwmon0 4 40000>;
> + tach-ch = /bits/ 8 <0x0d>;
> + };
> + fan-15 {
> + pwms = <&hwmon0 6 40000>;
> + tach-ch = /bits/ 8 <0x0f>;
> + };
> + fan-1 {
> + pwms = <&hwmon0 6 40000>;
> + tach-ch = /bits/ 8 <0x01>;
> + };
> + fan-0 {
> + pwms = <&hwmon0 10 40000>;
> + tach-ch = /bits/ 8 <0x00>;
> + };
> + fan-3 {
> + pwms = <&hwmon0 10 40000>;
> + tach-ch = /bits/ 8 <0x03>;
> + };
> + };
> + hwmon1: hwmon@2 {
As above.
Andrew
next prev parent reply other threads:[~2025-03-21 1:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 15:21 [PATCH v5 00/10] ARM: dts: aspeed: catalina: Update DTS to support Catalina PVT hardware Potin Lai
2025-03-20 15:21 ` [PATCH v5 01/10] ARM: dts: aspeed: catalina: Add IO Mezz board thermal sensor nodes Potin Lai
2025-03-20 15:21 ` [PATCH v5 02/10] ARM: dts: aspeed: catalina: Add Front IO board remote thermal sensor Potin Lai
2025-03-20 15:21 ` [PATCH v5 03/10] ARM: dts: aspeed: catalina: Add MP5990 power sensor node Potin Lai
2025-03-20 15:21 ` [PATCH v5 04/10] ARM: dts: aspeed: catalina: Add fan controller support Potin Lai
2025-03-20 15:21 ` [PATCH v5 05/10] ARM: dts: aspeed: catalina: Add second source " Potin Lai
2025-03-21 1:17 ` Andrew Jeffery [this message]
2025-03-20 15:21 ` [PATCH v5 06/10] ARM: dts: aspeed: catalina: Add second source HSC node support Potin Lai
2025-03-20 15:21 ` [PATCH v5 07/10] ARM: dts: aspeed: catalina: Remove INA238 and INA230 nodes Potin Lai
2025-03-20 15:21 ` [PATCH v5 08/10] ARM: dts: aspeed: catalina: Enable multi-master on additional I2C buses Potin Lai
2025-03-20 15:21 ` [PATCH v5 09/10] ARM: dts: aspeed: catalina: Update CBC FRU EEPROM I2C bus and address Potin Lai
2025-03-20 15:22 ` [PATCH v5 10/10] ARM: dts: aspeed: catalina: Enable MCTP support for NIC management Potin Lai
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=26a1d17c47c5ca6036dd58ac3b953daeec9f5ef8.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=potin.lai.pt@gmail.com \
--cc=potin.lai@quantatw.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
all inboxes | Powered by JetHome®