All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Selvamani Rajagopal" <Selvamani.Rajagopal@onsemi.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v9 08/11] onsemi: s2500: Add driver support for S2500 MAC-PHY
Date: Sat, 10 Oct 2026 17:12:33 +0000	[thread overview]
Message-ID: <sashiko-outbox-166772@kernel.org> (raw)
In-Reply-To: <20261009-s2500-mac-phy-support-v9-8-dcefe1d0bf0d@onsemi.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] net: ptp: max_adj exceeds 32-bit scaled_ppm limit
- [Low] net: ethtool: duplication of standard rx_dropped stat
--

commit 00c8e30757f8b1220a6ef1275c224d8bbca5148c
Author: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>

    onsemi: s2500: Add driver support for S2500 MAC-PHY
    
    Support for onsemi's S2500, 802.3 cg compliant Ethernet transceiver with
    integrated MAC-PHY.

diff --git a/drivers/net/ethernet/onsemi/s2500/s2500_ethtool.c b/drivers/net/ethernet/onsemi/s2500/s2500_ethtool.c
--- /dev/null
+++ b/drivers/net/ethernet/onsemi/s2500/s2500_ethtool.c
[ ... ]
> +static const char s2500_mac_stat_strings[][ETH_GSTRING_LEN] = {
> +	"rx_mismatch_drops",
> +};
> +
> +static const u8 s2500_mac_stat_map[S2500_NUM_MAC_STATS] = {
> +	S2500_MSTRXDROPPED_IDX,
> +};

[Severity: Low]
Does this regression duplicate a standard uAPI statistic? The network core
guidelines indicate that counters with standard representations must not be
exposed as private ethtool -S strings. Since there is a standard representation
for dropped frames, could this private string be removed to avoid duplication?

[ ... ]
diff --git a/drivers/net/ethernet/onsemi/s2500/s2500_hw_def.h b/drivers/net/ethernet/onsemi/s2500/s2500_hw_def.h
--- /dev/null
+++ b/drivers/net/ethernet/onsemi/s2500/s2500_hw_def.h
[ ... ]
> +/* Frequency adjust magnitude, 1 LSB = 0.000125 ppm = 1/8 ppb */
> +#define S2500_PTP_ADJ_MAX		GENMASK(27, 0)
> +#define S2500_PTP_MAX_ADJ_PPB		(S2500_PTP_ADJ_MAX / 8)
[ ... ]
diff --git a/drivers/net/ethernet/onsemi/s2500/s2500_ptp.c b/drivers/net/ethernet/onsemi/s2500/s2500_ptp.c
--- /dev/null
+++ b/drivers/net/ethernet/onsemi/s2500/s2500_ptp.c
[ ... ]
> +int s2500_ptp_register(struct s2500_info *priv)
> +{
> +	struct ptp_clock_info *info = &priv->ptp_clock_info;
> +	int ret;
> +
> +	info->max_adj = S2500_PTP_MAX_ADJ_PPB;

[Severity: Medium]
Will this regression cause the max_adj value to overflow on 32-bit
architectures? The driver advertises a max_adj of 268435455 / 8 = 33,554,431
PPB. The PTP subsystem converts PPB to scaled_ppm by multiplying by 65.536 and
passes the result as a signed long to the driver's adjfine callback.

On 32-bit architectures, 33554431 * 65.536 = 2199023243, which exceeds the
32-bit signed long maximum of 2147483647.

Could this mathematical wrap-around directly cause large positive frequency
adjustments to be passed as negative values into s2500_ptp_adjfine(), driving
severe clock drift in the opposite direction?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261009-s2500-mac-phy-support-v9-0-dcefe1d0bf0d@onsemi.com?part=8

  parent reply	other threads:[~2026-10-10 17:12 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 17:12 [PATCH net-next v9 00/11] Support for onsemi's S2500 10Base-T1S MAC-PHY Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 17:12 ` [PATCH net-next v9 01/11] dt-bindings: net: add onsemi's S2500 Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-09 17:12 ` [PATCH net-next v9 02/11] Documentation: networking: Add timestamp related APIs to OA TC6 framework Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 03/11] net: ethernet: oa_tc6: Move oa_tc6.c to its own directory Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-09 18:40   ` Selvamani Rajagopal
2026-10-10 17:12   ` sashiko-bot
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 04/11] net: ethernet: oa_tc6: Move constant definitions to header file Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 17:12   ` sashiko-bot
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 05/11] net: ethernet: oa_tc6: Support for hardware timestamp Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 17:12   ` sashiko-bot
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 06/11] net: ethernet: oa_tc6: Support for vendor specific MMS Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-09 18:43   ` Selvamani Rajagopal
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 07/11] net: phy: ncn26000: Enable enhanced noise immunity Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 08/11] onsemi: s2500: Add driver support for S2500 MAC-PHY Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-09 23:02   ` Randy Dunlap
2026-10-10 17:12   ` sashiko-bot [this message]
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 09/11] onsemi: s2500: Added selftest support to onsemi's S2500 driver Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 17:12   ` sashiko-bot
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 10/11] net: phy: ncn26000: Support for onsemi's S2500 internal phy Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 17:12   ` sashiko-bot
2026-10-10 19:40   ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 11/11] net: phy: ncn26000: Support for loopback Selvamani Rajagopal via B4 Relay
2026-10-09 17:12   ` Selvamani Rajagopal
2026-10-10 19:40   ` netdev-bot+sashiko

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=sashiko-outbox-166772@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Selvamani.Rajagopal@onsemi.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.