From: Jakub Kicinski <kuba@kernel.org>
To: Lorenz Brun <lorenz@brun.one>
Cc: Igor Russkikh <irusskikh@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: atlantic: support reading SFP module info
Date: Wed, 9 Oct 2024 17:56:16 -0700 [thread overview]
Message-ID: <20241009175616.39594837@kernel.org> (raw)
In-Reply-To: <20241006215028.79486-1-lorenz@brun.one>
On Sun, 6 Oct 2024 23:50:25 +0200 Lorenz Brun wrote:
> Add support for reading SFP module info and digital diagnostic
> monitoring data if supported by the module. The only Aquantia
> controller without an integrated PHY is the AQC100 which belongs to
> the B0 revision, that's why it's only implemented there.
>
> The register information was extracted from a diagnostic tool made
> publicly available by Dell, but all code was written from scratch by me.
>
> This has been tested to work with a variety of both optical and direct
> attach modules I had lying around and seems to work fine with all of
> them, including the diagnostics if supported by an optical module.
> All tests have been done with an AQC100 on an TL-NT521F card on firmware
> version 3.1.121 (current at the time of this patch).
> +static int aq_ethtool_get_module_info(struct net_device *ndev,
> + struct ethtool_modinfo *modinfo)
> +{
> + int err;
> + u8 compliance_val, dom_type;
> + struct aq_nic_s *aq_nic = netdev_priv(ndev);
nit:
Could you reverse the order of variable declarations?
We prefer longest to shortest lines.
> +
> + /* Module EEPROM is only supported for controllers with external PHY */
> + if (aq_nic->aq_nic_cfg.aq_hw_caps->media_type != AQ_HW_MEDIA_TYPE_FIBRE)
> + return -EOPNOTSUPP;
> +
> + if (!aq_nic->aq_hw_ops->hw_read_module_eeprom)
> + return -EOPNOTSUPP;
> +
> + err = aq_nic->aq_hw_ops->hw_read_module_eeprom(aq_nic->aq_hw,
> + SFF_8472_ID_ADDR, SFF_8472_COMP_ADDR, 1, &compliance_val);
> + if (err)
> + return err;
> +
> + err = aq_nic->aq_hw_ops->hw_read_module_eeprom(aq_nic->aq_hw,
> + SFF_8472_ID_ADDR, SFF_8472_DOM_TYPE_ADDR, 1, &dom_type);
> + if (err)
> + return err;
> +
> + if (dom_type & SFF_8472_ADDRESS_CHANGE_REQ_MASK || compliance_val == 0x00) {
> + modinfo->type = ETH_MODULE_SFF_8079;
> + modinfo->eeprom_len = ETH_MODULE_SFF_8079_LEN;
> + } else {
> + modinfo->type = ETH_MODULE_SFF_8472;
> + modinfo->eeprom_len = ETH_MODULE_SFF_8472_LEN;
> + }
> + return 0;
> +}
> +
> +static int aq_ethtool_get_module_eeprom(struct net_device *ndev,
> + struct ethtool_eeprom *ee, unsigned char *data)
> +{
> + int err;
> + unsigned int first, last, len;
> + struct aq_nic_s *aq_nic = netdev_priv(ndev);
nit: extra tab here
> + if (!aq_nic->aq_hw_ops->hw_read_module_eeprom)
> + return -EOPNOTSUPP;
> +
> + if (ee->len == 0)
> + return -EINVAL;
I don't think core will let that happen, you can remove the check
> + first = ee->offset;
> + last = ee->offset + ee->len;
> +
> + if (first < ETH_MODULE_SFF_8079_LEN) {
> + len = min_t(unsigned int, last, ETH_MODULE_SFF_8079_LEN);
AFAIU pure min() may work these days
> + len -= first;
> +
> + err = aq_nic->aq_hw_ops->hw_read_module_eeprom(aq_nic->aq_hw,
> + SFF_8472_ID_ADDR, first, len, data);
> + if (err)
> + return err;
> +
> + first += len;
> + data += len;
> + }
> + if (first < ETH_MODULE_SFF_8472_LEN && last > ETH_MODULE_SFF_8079_LEN) {
> + len = min_t(unsigned int, last, ETH_MODULE_SFF_8472_LEN);
> + len -= first;
> + first -= ETH_MODULE_SFF_8079_LEN;
> +
> + err = aq_nic->aq_hw_ops->hw_read_module_eeprom(aq_nic->aq_hw,
> + SFF_8472_DIAGNOSTICS_ADDR, first, len, data);
> + if (err)
> + return err;
> + }
> + return 0;
> +}
> +
> const struct ethtool_ops aq_ethtool_ops = {
> .supported_coalesce_params = ETHTOOL_COALESCE_USECS |
> ETHTOOL_COALESCE_MAX_FRAMES,
> @@ -1014,4 +1090,6 @@ const struct ethtool_ops aq_ethtool_ops = {
> .get_ts_info = aq_ethtool_get_ts_info,
> .get_phy_tunable = aq_ethtool_get_phy_tunable,
> .set_phy_tunable = aq_ethtool_set_phy_tunable,
> + .get_module_info = aq_ethtool_get_module_info,
> + .get_module_eeprom = aq_ethtool_get_module_eeprom,
> };
> +static int hw_atl_b0_read_module_eeprom(struct aq_hw_s *self, u8 dev_addr,
> + u8 reg_start_addr, int len, u8 *data)
> +{
> + int err;
> + int i, b;
> + u32 val;
> +
> + /* Wait for SMBUS0 to be idle */
> + err = readx_poll_timeout_atomic(hw_atl_smb0_bus_busy_get, self,
> + val, val == 0, 100U, 10000U);
Why atomic?
--
pw-bot: cr
prev parent reply other threads:[~2024-10-10 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 21:50 [PATCH] net: atlantic: support reading SFP module info Lorenz Brun
2024-10-10 0:56 ` Jakub Kicinski [this message]
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=20241009175616.39594837@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenz@brun.one \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).