mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Donald Shannon <donalds@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	joel@jms.id.au, andrew@codeconstruct.com.au,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org
Subject: Re: [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b
Date: Tue, 5 Aug 2025 11:18:12 -0700	[thread overview]
Message-ID: <5e5c8bd2-4c4b-4371-a6b2-d4d4359a4233@nvidia.com> (raw)
In-Reply-To: <20250724-affable-gorgeous-dragon-130ac6@kuoka>

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


  reply	other threads:[~2025-08-05 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 22:23 Donald Shannon
2025-07-23 22:23 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board Donald Shannon
2025-07-24  7:54   ` Krzysztof Kozlowski
2025-07-23 22:23 ` [PATCH v7 2/2] ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board Donald Shannon
2025-07-24  7:54 ` [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b Krzysztof Kozlowski
2025-08-05 18:18   ` Donald Shannon [this message]
2025-08-06  6:12     ` Krzysztof Kozlowski
2025-07-25  3:19 ` Rob Herring (Arm)
2025-07-25  3:25   ` Rob Herring
2025-07-31  2:11     ` Andrew Jeffery

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=5e5c8bd2-4c4b-4371-a6b2-d4d4359a4233@nvidia.com \
    --to=donalds@nvidia.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --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®