From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: "P.K. Lee" <pkleequanta@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
patrick@stwcx.xyz
Cc: Jerry.Lin@quantatw.com, Jason-Hsu@quantatw.com,
yang.chen@quantatw.com, p.k.lee@quantatw.com
Subject: Re: [PATCH v9 2/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC
Date: Mon, 21 Jul 2025 13:11:51 +0930 [thread overview]
Message-ID: <6b1ade72e11089b0fab13a4f6ef53a1ea65fa732.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250716094329.1069203-3-pkleequanta@gmail.com>
On Wed, 2025-07-16 at 17:43 +0800, P.K. Lee wrote:
> Add Linux device tree related to Meta (Facebook) Ventura specific
> devices connected to the BMC (AST2600) SoC. The purpose of Ventura is to
> detect liquid leakage from all compute trays, switch trays and rack
> sensors within the rack, log the events, and take necessary actions
> accordingly.
>
> Signed-off-by: P.K. Lee <pkleequanta@gmail.com>
> ---
> arch/arm/boot/dts/aspeed/Makefile | 1 +
> .../aspeed/aspeed-bmc-facebook-ventura.dts | 1553 +++++++++++++++++
> 2 files changed, 1554 insertions(+)
> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-ventura.dts
>
> diff --git a/arch/arm/boot/dts/aspeed/Makefile b/arch/arm/boot/dts/aspeed/Makefile
> index c4f064e4b073..5ed6042eea97 100644
> --- a/arch/arm/boot/dts/aspeed/Makefile
> +++ b/arch/arm/boot/dts/aspeed/Makefile
> @@ -27,6 +27,7 @@ dtb-$(CONFIG_ARCH_ASPEED) += \
> aspeed-bmc-facebook-minerva.dtb \
> aspeed-bmc-facebook-minipack.dtb \
> aspeed-bmc-facebook-tiogapass.dtb \
> + aspeed-bmc-facebook-ventura.dtb \
I'm hitting a conflict here, can you please rebase this series on top
of aspeed/dt from [1]?
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git/
> +
> + memory@80000000 {
> + device_type = "memory";
> + reg = <0x80000000 0x80000000>;
> + };
> +
> + p1v8_bmc_aux: regulator-p1v8-bmc-aux {
Can you please fix the indentation here?
> + compatible = "regulator-fixed";
> + regulator-name = "p1v8_bmc_aux";
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + regulator-always-on;
> + };
> +
> + p2v5_bmc_aux: regulator-p2v5-bmc-aux {
> + compatible = "regulator-fixed";
> + regulator-name = "p2v5_bmc_aux";
> + regulator-min-microvolt = <2500000>;
> + regulator-max-microvolt = <2500000>;
> + regulator-always-on;
> + };
> +
> + spi1_gpio: spi {
And again here?
Please check the entire devicetree for similar issues.
> + compatible = "spi-gpio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + sck-gpios = <&gpio0 ASPEED_GPIO(Z, 3) GPIO_ACTIVE_HIGH>;
> + mosi-gpios = <&gpio0 ASPEED_GPIO(Z, 4) GPIO_ACTIVE_HIGH>;
> + miso-gpios = <&gpio0 ASPEED_GPIO(Z, 5) GPIO_ACTIVE_HIGH>;
> + cs-gpios = <&gpio0 ASPEED_GPIO(Z, 0) GPIO_ACTIVE_LOW>;
> + num-chipselects = <1>;
> +
> + tpm@0 {
> + compatible = "infineon,slb9670", "tcg,tpm_tis-spi";
> + spi-max-frequency = <33000000>;
> + reg = <0>;
> + };
> + };
> +};
> +
[...]
> + i2c3mux0ch3: i2c@3 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <3>;
> +
> + // Fan Board 0 FRU
> + eeprom@56 {
> + compatible = "atmel,24c128";
> + reg = <0x56>;
> + };
> +
> + fan_leds_g1_gpio: gpio@21 {
Please make sure the devicetree meets the style guide[2], particularly
the order of nodes:
https://docs.kernel.org/devicetree/bindings/dts-coding-style.html#order-of-nodes
Here, devices should be listed in ascending order of address.
Please check the entire devicetree.
[2]: https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
Andrew
prev parent reply other threads:[~2025-07-21 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:43 [PATCH v9 0/2] Add Meta (Facebook) Ventura BMC (AST2600) P.K. Lee
2025-07-16 9:43 ` [PATCH v9 1/2] dt-bindings: arm: aspeed: add Meta Ventura board P.K. Lee
2025-07-16 9:48 ` Krzysztof Kozlowski
2025-07-16 9:43 ` [PATCH v9 2/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC P.K. Lee
2025-07-21 3:41 ` Andrew Jeffery [this message]
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=6b1ade72e11089b0fab13a4f6ef53a1ea65fa732.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=Jason-Hsu@quantatw.com \
--cc=Jerry.Lin@quantatw.com \
--cc=conor+dt@kernel.org \
--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=p.k.lee@quantatw.com \
--cc=patrick@stwcx.xyz \
--cc=pkleequanta@gmail.com \
--cc=robh@kernel.org \
--cc=yang.chen@quantatw.com \
/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).