mirror of https://lore.kernel.org/lkml/
 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>,
	<etanous@nvidia.com>, <joel@jms.id.au>, <krzk+dt@kernel.org>,
	<leohu@nvidia.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
	<openbmc@lists.ozlabs.org>, <robh@kernel.org>, <wthai@nvidia.com>
Subject: [PATCH v2 4/4] ARM: dts: aspeed: nvidia: gb200nvl: Enable MAC0 for BMC network
Date: Thu, 17 Jul 2025 08:58:57 +0000	[thread overview]
Message-ID: <20250717085857.2707150-1-wthai@nvidia.com> (raw)
In-Reply-To: <17cd5195-29d7-44db-8f3c-474dc5c3486b@lunn.ch>

>> +&mac0 {
>> +	status = "okay";
>> +	pinctrl-names = "default";
>> +	phy-mode = "rgmii-id";
>> +	max-speed = <1000>;

> The MAC is using rgmii. How can it do more than 1G?

>	Andrew

Thanks Andrew for quick reply !
Will fix this in the next version by removing it, because this MAC can negotiate with PHY.

      reply	other threads:[~2025-07-17  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16 18:21 [PATCH v2 0/4] ARM: dts: aspeed: nvidia: Update DTS to support GB200NVL hardware Willie Thai
2025-07-16 18:21 ` [PATCH v2 1/4] ARM: dts: aspeed: nvidia: gb200nvl: Add VCC Supply Willie Thai
2025-07-16 18:21 ` [PATCH v2 2/4] ARM: dts: aspeed: nvidia: gb200nvl: Enable i2c3 bus Willie Thai
2025-07-16 18:21 ` [PATCH v2 3/4] ARM: dts: aspeed: nvidia: gb200nvl: Repurpose the HMC gpio pin Willie Thai
2025-07-16 18:21 ` [PATCH v2 4/4] ARM: dts: aspeed: nvidia: gb200nvl: Enable MAC0 for BMC network Willie Thai
2025-07-16 20:03   ` Andrew Lunn
2025-07-17  8:58     ` Willie Thai [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=20250717085857.2707150-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=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=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®