[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <160008e2-f480-49c3-994e-a498e74eee23@lunn.ch>
Date: Tue, 26 Nov 2024 20:24:15 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jason Hsu <jasonhell19@...il.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
joel@....id.au, andrew@...econstruct.com.au, patrick@...cx.xyz,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
yang.chen@...ntatw.com, jerry.lin@...ntatw.com,
Jason Hsu <jason-hsu@...ntatw.com>
Subject: Re: [PATCH v4 2/2] ARM: dts: aspeed: ventura: add Meta Ventura BMC
> + // 88E6393X CONFIG FRU
> + eeprom@50 {
> + compatible = "atmel,24c64";
> + reg = <0x50>;
> + };
I just noticed this and it seems odd. MV88E6393X is a Marvell Ethernet
switch. It can have an eeprom, and if so, the mv88e6xxx driver will
export it via ethtool. It is not normally visible to Linux as an I2C
device, because it hangs off the switches I2C Bus.
Do you have some multi master going on?
I also don't see the switch itself here. I would expect it to be
listed in the MDIO node.
Andrew
Powered by blists - more mailing lists