[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d87d203c-cd81-43c6-8731-00ff564bbf2f@lunn.ch>
Date: Wed, 7 May 2025 16:17:38 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Wasim Nazir <quic_wasimn@...cinc.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Richard Cochran <richardcochran@...il.com>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
kernel@...cinc.com, kernel@....qualcomm.com
Subject: Re: [PATCH 0/8] qcom: Refactor sa8775p/qcs9100 based ride boards
> Ethernet card:
> - There are two variants of ethernet card each with different capabilities:
> - [Ethernet-v1] card contains:
> - 2x 1G RGMII phy, 2x 1G SGMII phy(enabled currently)
> - Total 4 phy supported, only 2 phy are enabled and it is used in ride.
> - [Ethernet-v2] card contains:
> - 2x 1G RGMII phy, 2x 2.5G HSGMII(enabled currently) & 10G PCIe
> based MAC+PHY controller
> - Total 5 phy supported, only 2 phy are enabled and it is used
> in ride-r3.
> - Either [Ethernet-v1] or [Ethernet-v2] is connected to backplain
> board via B2B connector.
Is it possible to identify the card, e.g. does it have an I2C EEPROM,
or some strapping resistors on the B2B bus?
I'm just wondering if DT overlays would be a better solution.
Andrew
Powered by blists - more mailing lists