.../bindings/arm/aspeed/aspeed.yaml | 1 + arch/arm/boot/dts/aspeed/Makefile | 1 + .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts | 1028 +++++++++++++++++ 3 files changed, 1030 insertions(+) create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
Patch 1 adds the binding for the NVIDIA GB200-UT3.0b platform. Patch 2 adds the device tree for the NVIDIA GB200-UT3.0b platform. This is an Aspeed AST2600 based unit testing platform for GB200. UT3.0b is different than nvidia-gb200nvl-bmc due to networking topology differences, additional gpio expanders, and voltage regulator gating some devices. Reference to Ast2600 SOC [1]. Reference to Blackwell GB200NVL Platform [2]. Link: https://www.aspeedtech.com/server_ast2600/ [1] Link: https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2] Signed-off-by: Donald Shannon <donalds@nvidia.com> --- 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 Changes v4 -> v5: - Resumed my patch after a pause - Don't plan to make this include of nvidia-gb200nvl-bmc due to some platform differences - Fixed io expanders that weren't gated by the 3.3V standby regulator - Fixed incorrect interrupt pin for one IO expander - Removed some IO expanders and I2C busses Changes v5 -> v6: - Fixed subject line - Added missing gpio-key compatible type to buttons Changes v6 -> v7: - Removed Acked-by Krzysztof --- Donald Shannon (2): dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board .../bindings/arm/aspeed/aspeed.yaml | 1 + arch/arm/boot/dts/aspeed/Makefile | 1 + .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts | 1028 +++++++++++++++++ 3 files changed, 1030 insertions(+) create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts base-commit: 05adbee3ad528100ab0285c15c91100e19e10138 -- 2.43.0
On Wed, 23 Jul 2025 15:23:48 -0700, Donald Shannon wrote:
> Patch 1 adds the binding for the NVIDIA GB200-UT3.0b platform.
> Patch 2 adds the device tree for the NVIDIA GB200-UT3.0b platform.
>
> This is an Aspeed AST2600 based unit testing platform for GB200.
> UT3.0b is different than nvidia-gb200nvl-bmc due to networking topology
> differences, additional gpio expanders, and voltage regulator gating
> some devices.
>
> Reference to Ast2600 SOC [1].
> Reference to Blackwell GB200NVL Platform [2].
>
> Link: https://www.aspeedtech.com/server_ast2600/ [1]
> Link: https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2]
> Signed-off-by: Donald Shannon <donalds@nvidia.com>
> ---
> 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
> Changes v4 -> v5:
> - Resumed my patch after a pause
> - Don't plan to make this include of nvidia-gb200nvl-bmc due to some
> platform differences
> - Fixed io expanders that weren't gated by the 3.3V standby regulator
> - Fixed incorrect interrupt pin for one IO expander
> - Removed some IO expanders and I2C busses
> Changes v5 -> v6:
> - Fixed subject line
> - Added missing gpio-key compatible type to buttons
> Changes v6 -> v7:
> - Removed Acked-by Krzysztof
> ---
>
> Donald Shannon (2):
> dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board
> ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board
>
> .../bindings/arm/aspeed/aspeed.yaml | 1 +
> arch/arm/boot/dts/aspeed/Makefile | 1 +
> .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts | 1028 +++++++++++++++++
> 3 files changed, 1030 insertions(+)
> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
>
>
> base-commit: 05adbee3ad528100ab0285c15c91100e19e10138
> --
> 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 05adbee3ad528100ab0285c15c91100e19e10138
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 20250723222350.200094-1-donalds@nvidia.com:
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/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/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: 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/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/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: 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/apb/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/apb/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: 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/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/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/dma-controller@1e79e000: failed to match any schema with compatible: ['aspeed,ast2600-udma']
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'anyOf' conditional failed, one must be fixed:
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'oneOf' conditional failed, one must be fixed:
'interrupts' is a required property
'interrupts-extended' is a required property
'gpios' is a required property
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'linux,code' is a required property
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: Unevaluated properties are not allowed ('gpio' was unexpected)
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'anyOf' conditional failed, one must be fixed:
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'oneOf' conditional failed, one must be fixed:
'interrupts' is a required property
'interrupts-extended' is a required property
'gpios' is a required property
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'linux,code' is a required property
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: Unevaluated properties are not allowed ('gpio' was unexpected)
from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
On Thu, Jul 24, 2025 at 10:19 PM Rob Herring (Arm) <robh@kernel.org> wrote:
>
>
> On Wed, 23 Jul 2025 15:23:48 -0700, Donald Shannon wrote:
> > Patch 1 adds the binding for the NVIDIA GB200-UT3.0b platform.
> > Patch 2 adds the device tree for the NVIDIA GB200-UT3.0b platform.
> >
> > This is an Aspeed AST2600 based unit testing platform for GB200.
> > UT3.0b is different than nvidia-gb200nvl-bmc due to networking topology
> > differences, additional gpio expanders, and voltage regulator gating
> > some devices.
> >
> > Reference to Ast2600 SOC [1].
> > Reference to Blackwell GB200NVL Platform [2].
> >
> > Link: https://www.aspeedtech.com/server_ast2600/ [1]
> > Link: https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2]
> > Signed-off-by: Donald Shannon <donalds@nvidia.com>
> > ---
> > 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
> > Changes v4 -> v5:
> > - Resumed my patch after a pause
> > - Don't plan to make this include of nvidia-gb200nvl-bmc due to some
> > platform differences
> > - Fixed io expanders that weren't gated by the 3.3V standby regulator
> > - Fixed incorrect interrupt pin for one IO expander
> > - Removed some IO expanders and I2C busses
> > Changes v5 -> v6:
> > - Fixed subject line
> > - Added missing gpio-key compatible type to buttons
> > Changes v6 -> v7:
> > - Removed Acked-by Krzysztof
> > ---
> >
> > Donald Shannon (2):
> > dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board
> > ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board
> >
> > .../bindings/arm/aspeed/aspeed.yaml | 1 +
> > arch/arm/boot/dts/aspeed/Makefile | 1 +
> > .../aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts | 1028 +++++++++++++++++
> > 3 files changed, 1030 insertions(+)
> > create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dts
> >
> >
> > base-commit: 05adbee3ad528100ab0285c15c91100e19e10138
> > --
> > 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 05adbee3ad528100ab0285c15c91100e19e10138
>
> 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 20250723222350.200094-1-donalds@nvidia.com:
>
> 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/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/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: 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/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/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: 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/apb/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/apb/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: 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/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/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/dma-controller@1e79e000: failed to match any schema with compatible: ['aspeed,ast2600-udma']
All of the below warnings you are introducing...
And yeah, all the ones above are existing, but I don't see a lot of
progress fixing them. It seems no one adding their board cares about
the SoC warnings given the lack of progress on aspeed stuff. Maybe new
boards need to be rejected without some improvements...
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'anyOf' conditional failed, one must be fixed:
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'oneOf' conditional failed, one must be fixed:
> 'interrupts' is a required property
> 'interrupts-extended' is a required property
> 'gpios' is a required property
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: 'linux,code' is a required property
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-power: Unevaluated properties are not allowed ('gpio' was unexpected)
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'anyOf' conditional failed, one must be fixed:
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'oneOf' conditional failed, one must be fixed:
> 'interrupts' is a required property
> 'interrupts-extended' is a required property
> 'gpios' is a required property
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: 'linux,code' is a required property
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
> arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-gb200-ut30b.dtb: buttons (gpio-keys): button-uid: Unevaluated properties are not allowed ('gpio' was unexpected)
> from schema $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
'gpio' has been deprecated for only about 10 years. Maybe 15...
Rob
On Thu, 2025-07-24 at 22:25 -0500, Rob Herring wrote: > > All of the below warnings you are introducing... > > And yeah, all the ones above are existing, but I don't see a lot of > progress fixing them. It seems no one adding their board cares about > the SoC warnings given the lack of progress on aspeed stuff. Maybe new > boards need to be rejected without some improvements... > I had an old branch with a series that reduces the warnings. I'll rebase it and tidy it up a bit wrt more recent binding submissions. Once it's mostly sensible I'll consider pointing people to it as suggestions for fixing existing issues on the path to getting their own devicetrees merged. Andrew
On Wed, Jul 23, 2025 at 03:23:48PM -0700, Donald Shannon wrote: > Patch 1 adds the binding for the NVIDIA GB200-UT3.0b platform. > Patch 2 adds the device tree for the NVIDIA GB200-UT3.0b platform. > > This is an Aspeed AST2600 based unit testing platform for GB200. > UT3.0b is different than nvidia-gb200nvl-bmc due to networking topology > differences, additional gpio expanders, and voltage regulator gating > some devices. > > Reference to Ast2600 SOC [1]. > Reference to Blackwell GB200NVL Platform [2]. > > Link: https://www.aspeedtech.com/server_ast2600/ [1] > Link: https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2] > Signed-off-by: Donald Shannon <donalds@nvidia.com> > --- > 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 > Changes v4 -> v5: > - Resumed my patch after a pause > - Don't plan to make this include of nvidia-gb200nvl-bmc due to some > platform differences > - Fixed io expanders that weren't gated by the 3.3V standby regulator > - Fixed incorrect interrupt pin for one IO expander > - Removed some IO expanders and I2C busses > Changes v5 -> v6: > - Fixed subject line > - Added missing gpio-key compatible type to buttons > Changes v6 -> v7: > - Removed Acked-by Krzysztof Why? You did not even give me chance to respond to your reply. Best regards, Krzysztof
On 7/24/25 00:54, Krzysztof Kozlowski wrote: > External email: Use caution opening links or attachments > > > On Wed, Jul 23, 2025 at 03:23:48PM -0700, Donald Shannon wrote: >> Patch 1 adds the binding for the NVIDIA GB200-UT3.0b platform. >> Patch 2 adds the device tree for the NVIDIA GB200-UT3.0b platform. >> >> This is an Aspeed AST2600 based unit testing platform for GB200. >> UT3.0b is different than nvidia-gb200nvl-bmc due to networking topology >> differences, additional gpio expanders, and voltage regulator gating >> some devices. >> >> Reference to Ast2600 SOC [1]. >> Reference to Blackwell GB200NVL Platform [2]. >> >> Link: https://www.aspeedtech.com/server_ast2600/ [1] >> Link: https://nvdam.widen.net/s/wwnsxrhm2w/blackwell-datasheet-3384703 [2] >> Signed-off-by: Donald Shannon <donalds@nvidia.com> >> --- >> 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 >> Changes v4 -> v5: >> - Resumed my patch after a pause >> - Don't plan to make this include of nvidia-gb200nvl-bmc due to some >> platform differences >> - Fixed io expanders that weren't gated by the 3.3V standby regulator >> - Fixed incorrect interrupt pin for one IO expander >> - Removed some IO expanders and I2C busses >> Changes v5 -> v6: >> - Fixed subject line >> - Added missing gpio-key compatible type to buttons >> Changes v6 -> v7: >> - Removed Acked-by Krzysztof > Why? You did not even give me chance to respond to your reply. > > Best regards, > Krzysztof Hi Krzysztof, I will reply here to keep our discussion together. I think that the issue was me using your kernel.org email and not your linaro.org email. I will fix this in the next patch series along with some fixes for the warnings from the other thread. Thanks, Don
On 05/08/2025 20:18, Donald Shannon wrote: >>> Changes v6 -> v7: >>> - Removed Acked-by Krzysztof >> Why? You did not even give me chance to respond to your reply. >> >> Best regards, >> Krzysztof > > Hi Krzysztof, > > I will reply here to keep our discussion together. > > I think that the issue was me using your kernel.org email and not your linaro.org email. > I will fix this in the next patch series along with some fixes for the warnings from the other thread. You should not "use email" at all. You MUST copy the tag as given, without modifying it or writing by yourself. Use for example `b4 trailers` for that. Or just copy paste. Best regards, Krzysztof
© 2016 - 2025 Red Hat, Inc.