From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Jacky Huang <jackyhuang@nvidia.com>,
joel@jms.id.au, robh@kernel.org, conor+dt@kernel.org,
andrew@lunn.ch
Cc: devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] ARM: dts: aspeed: Add NVIDIA VR-NVL BMC
Date: Wed, 22 Jul 2026 17:55:11 +0930 [thread overview]
Message-ID: <3b6aa85161702da4322cc361e500a90c832af6a7.camel@codeconstruct.com.au> (raw)
In-Reply-To: <3523fefc-8ba8-4512-b088-7a94a2df73f8@oss.qualcomm.com>
On Wed, 2026-07-22 at 10:21 +0200, Krzysztof Kozlowski wrote:
> On 22/07/2026 09:45, Andrew Jeffery wrote:
> > Hi Jacky,
> >
> > On Fri, 2026-07-10 at 14:46 +0900, Jacky Huang wrote:
> > > Add the device tree for the Aspeed AST2600 BMC for NVIDIA's Vera
> > > Rubin NVL compute platform.
> > >
> > > MAC0 uses phy-mode = "rgmii-id" because the on-board PHY supplies
> > > both RGMII internal delays. The matching U-Boot device tree does not
> > > enable SoC-side MAC clock delays, leaving the MAC internal delay at
> > > zero so the PHY-provided delay is not doubled by the MAC controller.
> > >
> > > The corresponding U-Boot change has been submitted to openbmc/u-boot:
> > > Link: https://lore.kernel.org/all/20260629105202.1417679-1-jackyhuang@nvidia.com/
> > >
> > > Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> > > Signed-off-by: Jacky Huang <jackyhuang@nvidia.com>
> > > ---
> > > v3: reword the &mac0 comment per Andrew Lunn's feedback.
> > >
> > > arch/arm/boot/dts/aspeed/Makefile | 1 +
> > > .../aspeed/aspeed-bmc-nvidia-vr-nvl-bmc.dts | 901 ++++++++++++++++++
> > > 2 files changed, 902 insertions(+)
> > > create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-vr-nvl-bmc.dts
> >
> > We now have scripts/dtc/dt-check-style, and going forward I'm asking
> > that all new devicetree submissions pass in strict mode.
>
> Thanks!
>
> >
> > Currently:
> >
> > $ ../scripts/dtc/dt-check-style --mode strict ../arch/arm/boot/dts/aspeed/aspeed-bmc-nvidia-vr-nvl-bmc.dts 2>&1 | wc -l
> > 152
> >
> > Can you please address those?
>
> Just a note: --strict might not be ready yet. It reports some false
> positives which need addressing (I have plans for this, but busy with
> other things...), so expectation currently is:
> 1. No warnings from standard mode
> 2. Review and investigate warnings from 'strict' mode, but do not fix
> them automatically without thinking
Understood.
Thanks,
Andrew
next prev parent reply other threads:[~2026-07-22 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:46 [PATCH v3 0/2] Add device tree for NVIDIA VR-NVL BMC Jacky Huang
2026-07-10 5:46 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: Add " Jacky Huang
2026-07-10 5:46 ` [PATCH v3 2/2] ARM: dts: " Jacky Huang
2026-07-10 6:02 ` sashiko-bot
2026-07-22 7:45 ` Andrew Jeffery
2026-07-22 8:21 ` Krzysztof Kozlowski
2026-07-22 8:25 ` Andrew Jeffery [this message]
2026-07-23 7:29 ` Jacky Huang
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=3b6aa85161702da4322cc361e500a90c832af6a7.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jackyhuang@nvidia.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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