[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4b1a9090-4134-4f77-a380-5ead03fd8ba8@app.fastmail.com>
Date: Mon, 18 Nov 2024 07:34:23 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Jacky Chou" <jacky_chou@...eedtech.com>, andrew+netdev@...n.ch,
"David S . Miller" <davem@...emloft.net>,
"Eric Dumazet" <edumazet@...gle.com>, "Jakub Kicinski" <kuba@...nel.org>,
"Paolo Abeni" <pabeni@...hat.com>, "Rob Herring" <robh@...nel.org>,
krzk+dt@...nel.org, "Conor Dooley" <conor+dt@...nel.org>,
"Philipp Zabel" <p.zabel@...gutronix.de>, Netdev <netdev@...r.kernel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [net-next v2 5/7] net: ftgmac100: add pin strap configuration for AST2700
On Mon, Nov 18, 2024, at 07:02, Jacky Chou wrote:
> @@ -351,6 +352,10 @@ static void ftgmac100_start_hw(struct ftgmac100 *priv)
> if (priv->netdev->features & NETIF_F_HW_VLAN_CTAG_RX)
> maccr |= FTGMAC100_MACCR_RM_VLAN;
>
> + if (of_device_is_compatible(priv->dev->of_node, "aspeed,ast2700-mac")
> &&
> + phydev && phydev->interface == PHY_INTERFACE_MODE_RMII)
> + maccr |= FTGMAC100_MACCR_RMII_ENABLE;
> +
> /* Hit the HW */
Is there a way to probe the presence of 64-bit addressing from
hardware registers? That would be nicer than triggering it from
the compatible string, given that any future SoC is likely
also 64-bit.
Arnd
Powered by blists - more mailing lists