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:

quoted

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 <redacted>
---
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