From: Donald Shannon <donalds@nvidia.com>
To: Conor Dooley <conor@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, etanous@nvidia.com
Subject: Re: [PATCH 2/2] ARM: dts: aspeed: Add NVIDIA VR144NVL board
Date: Thu, 21 Aug 2025 17:20:48 -0700 [thread overview]
Message-ID: <03741606-1ef2-4099-889e-2e0ef27cbb15@nvidia.com> (raw)
In-Reply-To: <20250821-baffling-immersion-e86971edb6e0@spud>
On 8/21/25 11:12, Conor Dooley wrote:
> On Wed, Aug 20, 2025 at 10:10:47PM -0700, Donald Shannon wrote:
>> +// I2C2
>> +// Baseboard 0 Management 1
>> +&i2c1 {
>> + clock-frequency = <400000>;
>> + status = "okay";
>> +
>> + i2c-mux@70 {
>> + compatible = "nxp,pca9548";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <0x70>;
>> + i2c-mux-idle-disconnect;
>> + vdd-supply = <®_3v3_stby>;
>> +
>> + c0uphy0: i2c@0 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <0>;
> Incorrect indent.
>
>> + };
>> +
>> + c0uphy2: i2c@1 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <1>;
>> + };
>> +
>> + c0unused2: i2c@2 {
> If these are unused, why are they here?
>
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <2>;
>> + };
>> +
>> + c0unused3: i2c@3 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <3>;
>> + };
>> +
>> + c0unused4: i2c@4 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <4>;
>> + };
>> +
>> + c0unused5: i2c@5 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <5>;
>> + };
>> +
>> + c0unused6: i2c@6 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <6>;
>> + };
>> +
>> + c0unused7: i2c@7 {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + reg = <7>;
>> + };
>> + };
Hi Connor,
I will remove those and we can add the busses back in for other platform variants' dts-es later if needed.
Thanks.
prev parent reply other threads:[~2025-08-22 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 5:10 [PATCH 0/2] Add NVIDIA VR144NVL board Donald Shannon
2025-08-21 5:10 ` [PATCH 1/2] dt-bindings: arm: aspeed: " Donald Shannon
2025-08-21 18:10 ` Conor Dooley
2025-08-21 5:10 ` [PATCH 2/2] ARM: dts: " Donald Shannon
2025-08-21 18:12 ` Conor Dooley
2025-08-22 0:20 ` Donald Shannon [this message]
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=03741606-1ef2-4099-889e-2e0ef27cbb15@nvidia.com \
--to=donalds@nvidia.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=etanous@nvidia.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@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