Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Willie Thai <wthai@nvidia.com>
To: <andrew@lunn.ch>
Cc: <andrew@codeconstruct.com.au>, <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>, <dkodihalli@nvidia.com>,
	<gpiccoli@igalia.com>, <joel@jms.id.au>, <kees@kernel.org>,
	<krzk+dt@kernel.org>, <krzk@kernel.org>, <leohu@nvidia.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-aspeed@lists.ozlabs.org>,
	<linux-hardening@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<maryang@nvidia.com>, <openbmc@lists.ozlabs.org>,
	<pmenzel@molgen.mpg.de>, <robh@kernel.org>, <tingkaic@nvidia.com>,
	<tony.luck@intel.com>, <wthai@nvidia.com>
Subject: [PATCH v3] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC
Date: Tue, 18 Mar 2025 19:14:24 +0000	[thread overview]
Message-ID: <20250318191424.4161850-1-wthai@nvidia.com> (raw)
In-Reply-To: <9ccc845b-9392-4a37-8bca-4f54997126ce@lunn.ch>

>> +&mac0 {
>> +     status = "okay";
>> +     pinctrl-names = "default";
>> +     phy-mode = "rgmii";
>> +     phy-handle = <&ethphy3>;
>> +     pinctrl-0 = <&pinctrl_rgmii1_default>; };

> Please read the discussion again. "rgmii" is probably equally wrong as "rgmii-rxid" you had in v1.

> Please talk with Aspeed and ask them the clean up the mess they made with RGMII delays. Until that happens, adding this node should wait.

Thanks for your feedback !
Talked with Aspeed SOC vendor, will skip this node in the next patch version till the delay issue get resolved.


  reply	other threads:[~2025-03-18 23:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  4:58 [PATCH v2] ARM: dts: aspeed: Add device tree for Nvidia's GB200NVL BMC Willie Thai
2025-03-12  7:49 ` Krzysztof Kozlowski
2025-03-19 11:24   ` Willie Thai
2025-03-19 19:28     ` Krzysztof Kozlowski
2025-03-12 12:11 ` Andrew Lunn
2025-03-18 19:14   ` Willie Thai [this message]
2025-03-12 13:07 ` Rob Herring (Arm)
2025-03-20 10:02   ` Willie Thai

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=20250318191424.4161850-1-wthai@nvidia.com \
    --to=wthai@nvidia.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dkodihalli@nvidia.com \
    --cc=gpiccoli@igalia.com \
    --cc=joel@jms.id.au \
    --cc=kees@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=leohu@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maryang@nvidia.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=robh@kernel.org \
    --cc=tingkaic@nvidia.com \
    --cc=tony.luck@intel.com \
    /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