[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79ddc7b9-ef26-4959-9a16-aa4e006eb145@roeck-us.net>
Date: Mon, 13 Oct 2025 17:20:57 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: rentao.bupt@...il.com
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...econstruct.com.au>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>, Tao Ren <taoren@...a.com>
Subject: Re: [PATCH v4 11/13] ARM: dts: aspeed: facebook-fuji: Include
facebook-fuji-data64.dts
Hi,
On Sun, Jul 27, 2025 at 10:56:13PM -0700, rentao.bupt@...il.com wrote:
> From: Tao Ren <rentao.bupt@...il.com>
>
> Include "facebook-fuji-data64.dts" in facebook-fuji dts to avoid
> duplicated code.
>
> Fuji-data64 and Fuji are identical except the BMC flash layout.
>
> Signed-off-by: Tao Ren <rentao.bupt@...il.com>
With this patch in the mainline kernel, the Ethernet interface I use for
testing does not come online when loading fuji-bmc in qemu.
Reverting this patch fixes the problem.
Looking into this patch,
> -
> -#include <dt-bindings/leds/common.h>
> -#include "ast2600-facebook-netbmc-common.dtsi"
> +#include "aspeed-bmc-facebook-fuji-data64.dts"
>
...
> -&mac3 {
> - status = "okay";
> - phy-mode = "rgmii";
> - phy-handle = <ðphy3>;
> - pinctrl-names = "default";
> - pinctrl-0 = <&pinctrl_rgmii4_default>;
> -};
I don't see this in aspeed-bmc-facebook-fuji-data64.dts, meaning that
interface is now disabled. Adding it back in fixes the problem.
Also, MAC3 is explicitly enabled for fuji-bmc in qemu.
Was the interface disabled on purpose ?
Thanks,
Guenter
Powered by blists - more mailing lists