public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Parthiban.Veerasooran@microchip.com>
To: <andrew@lunn.ch>
Cc: <piergiorgio.beruto@gmail.com>, <hkallweit1@gmail.com>,
	<linux@armlinux.org.uk>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] net: phy: phy-c45: add SQI and SQI+ support for OATC14 10Base-T1S PHYs
Date: Mon, 17 Nov 2025 05:43:01 +0000	[thread overview]
Message-ID: <7c0e51cf-df0b-4be1-851b-c91ea45f3380@microchip.com> (raw)
In-Reply-To: <4576bf3a-0945-4745-b7e9-3833cc45027a@lunn.ch>

Hi Andrew,

On 14/11/25 8:02 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
>> 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?

Good point — thanks for pointing it out.

Currently, ethtool reads the SQI value and displays it as part of the 
statistics. It looks like the current SNMP agent implementation isn’t 
polling the SQI value. However, it is possible that some vendors may 
implement this in their networks, in which case we might run into the 
issue of reading SQI capabilities multiple times.

To be on the safe side, and per your suggestion, I will cache/store the 
SQI capability details in the PHY device structure in the next version.

Best regards,
Parthiban V
> 
>          Andrew


  reply	other threads:[~2025-11-17  5:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 11:52 [PATCH net-next 0/2] Add SQI and SQI+ support for OATC14 10Base-T1S PHYs and Microchip T1S driver Parthiban Veerasooran
2025-11-13 11:52 ` [PATCH net-next 1/2] net: phy: phy-c45: add SQI and SQI+ support for OATC14 10Base-T1S PHYs Parthiban Veerasooran
2025-11-13 16:15   ` Andrew Lunn
2025-11-14  8:37     ` Parthiban.Veerasooran
2025-11-14 14:32       ` Andrew Lunn
2025-11-17  5:43         ` Parthiban.Veerasooran [this message]
2025-11-14  1:31   ` kernel test robot
2025-11-13 11:52 ` [PATCH net-next 2/2] net: phy: microchip_t1s: add SQI support for LAN867x Rev.D0 PHYs Parthiban Veerasooran
2025-11-13 13:39 ` [PATCH net-next 0/2] Add SQI and SQI+ support for OATC14 10Base-T1S PHYs and Microchip T1S driver Andrew Lunn
2025-11-14  5:19   ` Parthiban.Veerasooran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7c0e51cf-df0b-4be1-851b-c91ea45f3380@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=piergiorgio.beruto@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox