Skip to contentSkip to conversation

ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform BMC

PATCH In review Donald Shannon 4 participants 7 messages Jun 11, 2025 – Jun 13, 2025

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH v4 1/1 ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform BMC

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform. Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

---
Changes v1 -> v2:
- Changed phy-mode to rgmii-id [Lunn]
- Removed redundant max-speed for mac0 [Lunn]
- Fixed typo from gb200nvl to gb200 in Makefile
Changes v2 -> v3:
- Fixed whitespace issues [Krzysztof]
- Fixed schema validation issues from my end ( there are still issues with the aspeed dtsi file that are not related to this new dts) [Herring]
- Reordered to follow style guide [Krzysztof]
- Removed redundant status okays
- Changed vcc to vdd for the power gating on the gpio expanders
Changes v3 -> v4:
- Added changelog [Krzysztof]
- Added nvidia,gb200-ut30b board binding [Krzysztof]
- Removed unused imports
- Reordered a couple other style guide violations
- Added back in a couple needed "status okay"s
---

Donald Shannon (1):
ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform
BMC

 .../bindings/arm/aspeed/aspeed.yaml           |    1 +
 arch/arm/boot/dts/aspeed/Makefile             |    1 +
 .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154 +++++++++++++++++
 3 files changed, 1156 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts

base-commit: 460178e842c7a1e48a06df684c66eb5fd630bcf7

Signature · 1 line
2.43.0
#1 lore raw

PATCH v4 1/1 ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform BMC

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform. Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

---
Changes v1 -> v2:
- Changed phy-mode to rgmii-id [Lunn]
- Removed redundant max-speed for mac0 [Lunn]
- Fixed typo from gb200nvl to gb200 in Makefile
Changes v2 -> v3:
- Fixed whitespace issues [Krzysztof]
- Fixed schema validation issues from my end ( there are still issues with the aspeed dtsi file that are not related to this new dts) [Herring]
- Reordered to follow style guide [Krzysztof]
- Removed redundant status okays
- Changed vcc to vdd for the power gating on the gpio expanders
Changes v3 -> v4:
- Added changelog [Krzysztof]
- Added nvidia,gb200-ut30b board binding [Krzysztof]
- Removed unused imports
- Reordered a couple other style guide violations
- Added back in a couple needed "status okay"s

---
 .../bindings/arm/aspeed/aspeed.yaml           |    1 +
 arch/arm/boot/dts/aspeed/Makefile             |    1 +
 .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154 +++++++++++++++++
 3 files changed, 1156 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml +1 -0
index a3736f134130..420fabf05b24 100644
@@ -98,6 +98,7 @@ properties:
               - inventec,starscream-bmc
               - inventec,transformer-bmc
               - jabil,rbp-bmc
+              - nvidia,gb200-ut30b
               - nvidia,gb200nvl-bmc
               - qcom,dc-scm-v1-bmc
               - quanta,s6q-bmc
arch/arm/boot/dts/aspeed/Makefile +1 -0
index b3170fdd3096..1101bc74e8c8 100644
@@ -51,6 +51,7 @@ dtb-$(CONFIG_ARCH_ASPEED) += \
 	aspeed-bmc-lenovo-hr855xg2.dtb \
 	aspeed-bmc-microsoft-olympus.dtb \
 	aspeed-bmc-nvidia-gb200nvl-bmc.dtb \
+	aspeed-bmc-nvidia-gb200-ut30b.dtb \
 	aspeed-bmc-opp-lanyang.dtb \
 	aspeed-bmc-opp-mowgli.dtb \
 	aspeed-bmc-opp-nicole.dtb \
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts new file +1154 -0

1,154 lines not on this page · raw message

Signature · 1 line
2.43.0
#2 lore raw

Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml

Quoted 37 lines · Donald Shannon

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform. Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

---
Changes v1 -> v2:
- Changed phy-mode to rgmii-id [Lunn]
- Removed redundant max-speed for mac0 [Lunn]
- Fixed typo from gb200nvl to gb200 in Makefile
Changes v2 -> v3:
- Fixed whitespace issues [Krzysztof]
- Fixed schema validation issues from my end ( there are still issues with the aspeed dtsi file that are not related to this new dts) [Herring]
- Reordered to follow style guide [Krzysztof]
- Removed redundant status okays
- Changed vcc to vdd for the power gating on the gpio expanders
Changes v3 -> v4:
- Added changelog [Krzysztof]
- Added nvidia,gb200-ut30b board binding [Krzysztof]
- Removed unused imports
- Reordered a couple other style guide violations
- Added back in a couple needed "status okay"s

---
 .../bindings/arm/aspeed/aspeed.yaml           |    1 +
 arch/arm/boot/dts/aspeed/Makefile             |    1 +
 .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154 +++++++++++++++++
 3 files changed, 1156 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml +0 -0
index a3736f134130..420fabf05b24 100644

Please run scripts/checkpatch.pl on the patches and fix reported warnings. After that, run also 'scripts/checkpatch.pl --strict' on the patches and (probably) fix more warnings. Some warnings can be ignored, especially from --strict run, but the code here looks like it needs a fix. Feel free to get in touch if the warning is not clear.

You already got this comment, didn't you?

Best regards,
Krzysztof

maintainer
#3 lore raw
In reply to Donald Shannon

Hi Donald,

In addition to addressing Krzysztof's comments regarding checkpatch:

Quoted 2 lines · Donald Shannon

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform.

Can you add some words contrasting this platform to the one submitted by Willie?

https://lore.kernel.org/all/[email protected]/

Quoted 7 lines

Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

Link:
https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2]

Please omit the blank line here so the Link: tags are part of the trailer.

Quoted 35 lines

---
Changes v1 -> v2:
  - Changed phy-mode to rgmii-id [Lunn]
  - Removed redundant max-speed for mac0 [Lunn]
  - Fixed typo from gb200nvl to gb200 in Makefile Changes v2 -> v3:
  - Fixed whitespace issues [Krzysztof]
  - Fixed schema validation issues from my end ( there are still issues with the aspeed dtsi file that are not related to this new dts) [Herring]
  - Reordered to follow style guide [Krzysztof]
  - Removed redundant status okays
  - Changed vcc to vdd for the power gating on the gpio expanders Changes v3 -> v4:
  - Added changelog [Krzysztof]
  - Added nvidia,gb200-ut30b board binding [Krzysztof]
  - Removed unused imports
  - Reordered a couple other style guide violations
  - Added back in a couple needed "status okay"s
---
 .../bindings/arm/aspeed/aspeed.yaml           |    1 + arch/arm/boot/dts/aspeed/Makefile             |    1 + .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154
+++++++++++++++++

 3 files changed, 1156 insertions(+)

 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200- ut30b.dts

Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml +0 -0
index a3736f134130..420fabf05b24 100644
@@ -98,6 +98,7 @@ properties:
Quoted 4 lines

               - inventec,starscream-bmc
               - inventec,transformer-bmc
               - jabil,rbp-bmc
+              - nvidia,gb200-ut30b

For what it's worth, checkpatch reports at least the following:

167: WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst 180: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
193: WARNING: DT compatible string "nvidia,gb200-ut30b" appears un-documented -- check ./Documentation/devicetree/bindings/

Thanks,

Andrew

#4 lore raw

Hi Andrew and Krzysztof,

The difference in this device tree is adding more GPIO expanders and changing the networking.

Would it be best practice to create a new device binding (in this case nvidia,gb200-ut30b), even if it is just a slight modification on gb200nvl-bmc? Or can I reuse the gb200nvl-bmc compatible string and avoid the yaml binding change all together since it would share the same drivers?

Donald Shannon
Data Center Systems
NVIDIA<http://www.nvidia.com/>

From: Andrew Jeffery <[email protected]>
Date: Thursday, June 12, 2025 at 00:56
To: Donald Shannon <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>
Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, Ed Tanous <[email protected]>
Subject: Re: [PATCH v4 1/1] ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform BMC

External email: Use caution opening links or attachments

Hi Donald,

In addition to addressing Krzysztof's comments regarding checkpatch:

Quoted 2 lines · Donald Shannon

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform.

Can you add some words contrasting this platform to the one submitted by Willie?

https://lore.kernel.org/all/[email protected]/

Quoted 7 lines

Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

Link:
https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2]

Please omit the blank line here so the Link: tags are part of the trailer.

Quoted 35 lines

---
Changes v1 -> v2:
- Changed phy-mode to rgmii-id [Lunn]
- Removed redundant max-speed for mac0 [Lunn]
- Fixed typo from gb200nvl to gb200 in Makefile
Changes v2 -> v3:
- Fixed whitespace issues [Krzysztof]
- Fixed schema validation issues from my end ( there are still
issues with the aspeed dtsi file that are not related to this new dts) [Herring]
- Reordered to follow style guide [Krzysztof]
- Removed redundant status okays
- Changed vcc to vdd for the power gating on the gpio expanders
Changes v3 -> v4:
- Added changelog [Krzysztof]
- Added nvidia,gb200-ut30b board binding [Krzysztof]
- Removed unused imports
- Reordered a couple other style guide violations
- Added back in a couple needed "status okay"s

---
 .../bindings/arm/aspeed/aspeed.yaml           |    1 +
 arch/arm/boot/dts/aspeed/Makefile             |    1 +
 .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154
+++++++++++++++++
 3 files changed, 1156 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-

ut30b.dts

Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml +0 -0
index a3736f134130..420fabf05b24 100644

Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml properties: · line 101

Quoted 4 lines
Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml +1 -0
@@ -98,6 +98,7 @@ properties:
               - inventec,starscream-bmc
               - inventec,transformer-bmc
               - jabil,rbp-bmc
+              - nvidia,gb200-ut30b

For what it's worth, checkpatch reports at least the following:

167: WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst 180: WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
193: WARNING: DT compatible string "nvidia,gb200-ut30b" appears un-documented -- check ./Documentation/devicetree/bindings/

Thanks,

Andrew

maintainer
#5 lore raw
Quoted 4 lines · Donald Shannon

Hi Andrew and Krzysztof,

The difference in this device tree is adding more GPIO expanders and changing the networking.

Can you please include a description of these differences in the commit message?

Quoted 6 lines

Would it be best practice to create a new device binding (in this case nvidia,gb200-ut30b), even if it is just a slight modification on gb200nvl-bmc? Or can I reuse the gb200nvl-bmc compatible string and avoid the yaml binding change all together since it would share the same drivers?

You can include the aspeed-bmc-nvidia-gb200nvl-bmc.dts file and override the nodes where the differences lie if that helps. There are existing examples of this strategy, for instance:

   $ git grep '^#include .*\.dts"$' arch/arm/boot/dts/aspeed/
   arch/arm/boot/dts/aspeed/aspeed-ast2600-evb-a1.dts:#include "aspeed-ast2600-evb.dts"
   arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-blueridge-4u.dts:#include "aspeed-bmc-ibm-blueridge.dts"
   arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier-1s4u.dts:#include "aspeed-bmc-ibm-rainier-4u.dts"
   arch/arm/boot/dts/aspeed/aspeed-bmc-ibm-rainier-4u.dts:#include "aspeed-bmc-ibm-rainier.dts"

Whether or not the differences warrant a separate compatible - I'm not sure.

Andrew

#6 lore raw
In reply to Donald Shannon
Quoted 39 lines · Donald Shannon

The GB200NVL UT3.0b BMC is an Aspeed Ast2600 based BMC for Nvidia Blackwell GB200NVL platform. Reference to Ast2600 SOC [1].
Reference to Blackwell GB200NVL Platform [2].

---
Changes v1 -> v2:
- Changed phy-mode to rgmii-id [Lunn]
- Removed redundant max-speed for mac0 [Lunn]
- Fixed typo from gb200nvl to gb200 in Makefile
Changes v2 -> v3:
- Fixed whitespace issues [Krzysztof]
- Fixed schema validation issues from my end ( there are still issues with the aspeed dtsi file that are not related to this new dts) [Herring]
- Reordered to follow style guide [Krzysztof]
- Removed redundant status okays
- Changed vcc to vdd for the power gating on the gpio expanders
Changes v3 -> v4:
- Added changelog [Krzysztof]
- Added nvidia,gb200-ut30b board binding [Krzysztof]
- Removed unused imports
- Reordered a couple other style guide violations
- Added back in a couple needed "status okay"s
---

Donald Shannon (1):
ARM: dts: aspeed: Add device tree for Nvidia's GB200 UT3.0b platform
BMC

 .../bindings/arm/aspeed/aspeed.yaml           |    1 +
 arch/arm/boot/dts/aspeed/Makefile             |    1 +
 .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts  | 1154 +++++++++++++++++
 3 files changed, 1156 insertions(+)
 create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
Quoted 6 lines

base-commit: 460178e842c7a1e48a06df684c66eb5fd630bcf7 --
2.43.0

My bot found new DTB warnings on the .dts files added or changed in this series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date:

  pip3 install dtschema --upgrade

This patch series was applied (using b4) to base:
Base: using specified base-commit 460178e842c7a1e48a06df684c66eb5fd630bcf7

If this is not the correct base, please add 'base-commit' tag (or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/aspeed/' for [email protected]:

arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dtb: syscon@1e6e2000 (aspeed,ast2600-scu): 'smp-memram@180' does not match any of the regexes: '^interrupt-controller@[0-9a-f]+$', '^p2a-control@[0-9a-f]+$', '^pinctrl(@[0-9a-f]+)?$', '^pinctrl-[0-9]+$', '^silicon-id@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/mfd/aspeed,ast2x00-scu.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: timer (arm,armv7-timer): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/timer/arm,arch_timer.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /sdram@1e6e0000: failed to match any schema with compatible: ['aspeed,ast2600-sdram-edac', 'syscon']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: bus@1e600000 (aspeed,ast2600-ahbc): compatible: ['aspeed,ast2600-ahbc', 'syscon'] is too long
from schema $id: http://devicetree.org/schemas/bus/aspeed,ast2600-ahbc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: syscon@1e6e2000 (aspeed,ast2600-scu): 'smp-memram@180' does not match any of the regexes: '^interrupt-controller@[0-9a-f]+$', '^p2a-control@[0-9a-f]+$', '^pinctrl(@[0-9a-f]+)?$', '^pinctrl-[0-9]+$', '^silicon-id@[0-9a-f]+$'
from schema $id: http://devicetree.org/schemas/mfd/aspeed,ast2x00-scu.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e6e0000/syscon@1e6e2000/smp-memram@180: failed to match any schema with compatible: ['aspeed,ast2600-smpmem'] arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e6e0000/display@1e6e6000: failed to match any schema with compatible: ['aspeed,ast2600-gfx', 'syscon']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: adc@1e6e9000 (aspeed,ast2600-adc0): 'interrupts' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/iio/adc/aspeed,ast2600-adc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: adc@1e6e9100 (aspeed,ast2600-adc1): 'interrupts' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/iio/adc/aspeed,ast2600-adc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: crypto@1e6fa000 (aspeed,ast2600-acry): 'aspeed,ahbc' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/crypto/aspeed,ast2600-acry.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: sdc@1e740000 (aspeed,ast2600-sd-controller): sdhci@1e740100:compatible: ['aspeed,ast2600-sdhci', 'sdhci'] is too long
from schema $id: http://devicetree.org/schemas/mmc/aspeed,sdhci.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: sdc@1e740000 (aspeed,ast2600-sd-controller): sdhci@1e740200:compatible: ['aspeed,ast2600-sdhci', 'sdhci'] is too long
from schema $id: http://devicetree.org/schemas/mmc/aspeed,sdhci.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/sdc@1e740000/sdhci@1e740100: failed to match any schema with compatible: ['aspeed,ast2600-sdhci', 'sdhci']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/sdc@1e740000/sdhci@1e740200: failed to match any schema with compatible: ['aspeed,ast2600-sdhci', 'sdhci']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e780000/timer@1e782000: failed to match any schema with compatible: ['aspeed,ast2600-timer']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: lpc@1e789000 (aspeed,ast2600-lpc-v2): reg-io-width: 4 is not of type 'object'
from schema $id: http://devicetree.org/schemas/mfd/aspeed-lpc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: lpc@1e789000 (aspeed,ast2600-lpc-v2): lpc-snoop@80: 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/mfd/aspeed-lpc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: kcs@24 (aspeed,ast2500-kcs-bmc-v2): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/ipmi/aspeed,ast2400-kcs-bmc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: kcs@28 (aspeed,ast2500-kcs-bmc-v2): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/ipmi/aspeed,ast2400-kcs-bmc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: kcs@2c (aspeed,ast2500-kcs-bmc-v2): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/ipmi/aspeed,ast2400-kcs-bmc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: kcs@114 (aspeed,ast2500-kcs-bmc-v2): 'clocks' does not match any of the regexes: '^pinctrl-[0-9]+$'
from schema $id: http://devicetree.org/schemas/ipmi/aspeed,ast2400-kcs-bmc.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e780000/lpc@1e789000/lhc@a0: failed to match any schema with compatible: ['aspeed,ast2600-lhc']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e780000/lpc@1e789000/ibt@140: failed to match any schema with compatible: ['aspeed,ast2600-ibt-bmc']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: fsi@1e79b000 (aspeed,ast2600-fsi-master): compatible: ['aspeed,ast2600-fsi-master', 'fsi-master'] is too long
from schema $id: http://devicetree.org/schemas/fsi/aspeed,ast2600-fsi-master.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e790000/fsi@1e79b000: failed to match any schema with compatible: ['aspeed,ast2600-fsi-master', 'fsi-master'] arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: fsi@1e79b100 (aspeed,ast2600-fsi-master): compatible: ['aspeed,ast2600-fsi-master', 'fsi-master'] is too long
from schema $id: http://devicetree.org/schemas/fsi/aspeed,ast2600-fsi-master.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e790000/fsi@1e79b100: failed to match any schema with compatible: ['aspeed,ast2600-fsi-master', 'fsi-master'] arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: /ahb/apb@1e790000/dma-controller@1e79e000: failed to match any schema with compatible: ['aspeed,ast2600-udma']