From: Rebecca Cran <rebecca@bsdio.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: 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>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: aspeed: add device tree for ASRock Rack ALTRAD8 BMC
Date: Tue, 16 Sep 2025 12:40:15 -0600 [thread overview]
Message-ID: <92bcdac9-44b1-4fc8-892a-01ef0ed0b7e0@bsdio.com> (raw)
In-Reply-To: <74e68c53-2696-4f86-97d3-c0b0a74d4669@lunn.ch>
On 9/15/25 18:37, Andrew Lunn wrote:
> And does it have a PHY? On an MDIO bus? Unless i'm mistaken, you don't
> describe the PHY, a phy-handle pointing to the PHY, and don't have
> phy-mode = 'rgmii-id'.
I've been trying to figure this out. Yes, it's connected to a PHY (an
RTL8211E).
At the moment it's being detected by OpenBMC as:
ftgmac100 1e680000.ethernet: Read MAC address 9c:6b:00:43:0b:bd from
device tree
RTL8211E Gigabit Ethernet 1e680000.ethernet--1:00: attached PHY driver
(mii_bus:phy_addr=1e680000.ethernet--1:00, irq=POLL)
ftgmac100 1e680000.ethernet eth1: irq 43, mapped at 7e548db4
ftgmac100 1e680000.ethernet eth1: Link is Up - 1Gbps/Full - flow control
rx/tx
aspeed-g5.dtsi has:
mac1: ethernet@1e680000 {
compatible = "aspeed,ast2500-mac", "faraday,ftgmac100";
reg = <0x1e680000 0x180>;
interrupts = <3>;
clocks = <&syscon ASPEED_CLK_GATE_MAC2CLK>;
status = "disabled";
};
It doesn't define a PHY, but I presume I can't define one without it
conflicting with the definition of mac1.
--
Rebecca Cran
next prev parent reply other threads:[~2025-09-16 23:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 5:10 [PATCH 0/2] Add device tree for ASRock Rack ALTRAD8 BMC Rebecca Cran
2025-09-11 5:10 ` [PATCH 1/2] dt-bindings: arm: aspeed: add ASRock Rack ALTRAD8 board Rebecca Cran
2025-09-11 6:29 ` Krzysztof Kozlowski
2025-09-11 5:10 ` [PATCH 2/2] ARM: dts: aspeed: add device tree for ASRock Rack ALTRAD8 BMC Rebecca Cran
2025-09-11 6:29 ` Krzysztof Kozlowski
2025-09-12 23:37 ` Rebecca Cran
2025-09-15 4:51 ` Andrew Jeffery
2025-09-11 14:09 ` Andrew Lunn
2025-09-16 0:26 ` Rebecca Cran
2025-09-16 0:37 ` Andrew Lunn
2025-09-16 18:40 ` Rebecca Cran [this message]
2025-09-16 19:07 ` Andrew Lunn
2025-09-16 21:22 ` Rebecca Cran
2025-09-16 22:05 ` Andrew Lunn
2025-09-15 5:02 ` Andrew Jeffery
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=92bcdac9-44b1-4fc8-892a-01ef0ed0b7e0@bsdio.com \
--to=rebecca@bsdio.com \
--cc=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=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