[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4576bf3a-0945-4745-b7e9-3833cc45027a@lunn.ch>
Date: Fri, 14 Nov 2025 15:32:38 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Parthiban.Veerasooran@...rochip.com
Cc: piergiorgio.beruto@...il.com, hkallweit1@...il.com,
linux@...linux.org.uk, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 1/2] net: phy: phy-c45: add SQI and SQI+ support
for OATC14 10Base-T1S PHYs
> If I understand correctly, do you mean to store the capability details
> in the phydev structure when genphy_c45_oatc14_get_sqi_max() is called,
> and then use them in the genphy_c45_oatc14_get_sqi() function?
>
> In that case, I may need to introduce new parameters in the phydev
> structure. Do you think introducing new parameters in the phydev
> structure is still necessary for this?
I'm not sure it is worth it. Do we expect an SNMP agent polling the
SQI value once per second? Once per minute? One extra read per minute
costs nothing. If it was happening more frequently, then it might be
worth caching the capabilities.
How do you see this being used?
Andrew
Powered by blists - more mailing lists