From: Willie Thai <wthai@nvidia.com>
To: <wthai@nvidia.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
"Deepak Kodihalli" <dkodihalli@nvidia.com>,
Ed Tanous <etanous@nvidia.com>, Leo Huang <leohu@nvidia.com>
Subject: [PATCH 0/3] ARM: dts: aspeed: nvidia: Update DTS to support GB200NVL hardware
Date: Sun, 25 May 2025 18:20:16 +0000 [thread overview]
Message-ID: <20250525-dts-v1-0-9ac63ad3bf15@nvidia.com> (raw)
Update the DTS file for the GB200NVL hardware change.
Signed-off-by: Deepak Kodihalli <dkodihalli@nvidia.com>
Signed-off-by: Ed Tanous <etanous@nvidia.com>
Signed-off-by: Leo Huang <leohu@nvidia.com>
Signed-off-by: Willie Thai <wthai@nvidia.com>
Signed-off-by: Willie Thai <wthai@nvidia.com>
---
Willie Thai (3):
ARM: dts: aspeed: nvidia: gb200nvl: Add VCC Supply
ARM: dts: aspeed: nvidia: gb200nvl: Enable i2c3 bus
ARM: dts: aspeed: nvidia: gb200nvl: Repurpose the HMC gpio pin
.../dts/aspeed/aspeed-bmc-nvidia-gb200nvl-bmc.dts | 39 ++++++++++++++++++++--
1 file changed, 37 insertions(+), 2 deletions(-)
---
base-commit: 13c9c6eabf033ed4f369ad4d29bdc58ed4a411e3
change-id: 20250525-dts-8eca0cb6dfae
Best regards,
--
Willie Thai <wthai@nvidia.com>
next reply other threads:[~2025-05-25 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 18:20 Willie Thai [this message]
2025-05-25 18:20 ` [PATCH 1/3] ARM: dts: aspeed: nvidia: gb200nvl: Add VCC Supply Willie Thai
2025-05-25 18:20 ` [PATCH 2/3] ARM: dts: aspeed: nvidia: gb200nvl: Enable i2c3 bus Willie Thai
2025-05-25 18:20 ` [PATCH 3/3] ARM: dts: aspeed: nvidia: gb200nvl: Repurpose the HMC gpio pin Willie Thai
2025-05-27 17:56 ` [PATCH 0/3] ARM: dts: aspeed: nvidia: Update DTS to support GB200NVL hardware Rob Herring (Arm)
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=20250525-dts-v1-0-9ac63ad3bf15@nvidia.com \
--to=wthai@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dkodihalli@nvidia.com \
--cc=etanous@nvidia.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=leohu@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.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®