From: Simon Horman <horms@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ariel Elior <aelior@marvell.com>,
Manish Chopra <manishc@marvell.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next v4 3/9] net: qlogic: qede: Use linkmode helpers for EEE
Date: Tue, 20 Feb 2024 12:44:05 +0000 [thread overview]
Message-ID: <20240220124405.GB40273@kernel.org> (raw)
In-Reply-To: <20240218-keee-u32-cleanup-v4-3-71f13b7c3e60@lunn.ch>
On Sun, Feb 18, 2024 at 11:07:00AM -0600, Andrew Lunn wrote:
> Make use of the existing linkmode helpers for bit manipulation of EEE
> advertise, support and link partner support. The aim is to drop the
> restricted _u32 variants in the near future.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Thanks Andrew,
the nit below notwithstanding this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
> ---
> drivers/net/ethernet/qlogic/qede/qede_ethtool.c | 60 ++++++++++++++++---------
> 1 file changed, 38 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/net/ethernet/qlogic/qede/qede_ethtool.c b/drivers/net/ethernet/qlogic/qede/qede_ethtool.c
...
> @@ -1812,9 +1820,12 @@ static int qede_get_eee(struct net_device *dev, struct ethtool_keee *edata)
>
> static int qede_set_eee(struct net_device *dev, struct ethtool_keee *edata)
> {
> + __ETHTOOL_DECLARE_LINK_MODE_MASK(supported) = {};
> + __ETHTOOL_DECLARE_LINK_MODE_MASK(tmp) = {};
> struct qede_dev *edev = netdev_priv(dev);
> struct qed_link_output current_link;
> struct qed_link_params params;
> + bool unsupp;
>
> if (!edev->ops->common->can_link_change(edev->cdev)) {
> DP_INFO(edev, "Link settings are not allowed to be changed\n");
> @@ -1832,21 +1843,26 @@ static int qede_set_eee(struct net_device *dev, struct ethtool_keee *edata)
> memset(¶ms, 0, sizeof(params));
> params.override_flags |= QED_LINK_OVERRIDE_EEE_CONFIG;
>
> - if (!(edata->advertised_u32 & (ADVERTISED_1000baseT_Full |
> - ADVERTISED_10000baseT_Full)) ||
> - ((edata->advertised_u32 & (ADVERTISED_1000baseT_Full |
> - ADVERTISED_10000baseT_Full)) !=
> - edata->advertised_u32)) {
> + linkmode_set_bit(ETHTOOL_LINK_MODE_10000baseT_Full_BIT,
> + supported);
> + linkmode_set_bit(ETHTOOL_LINK_MODE_1000baseT_Full_BIT,
> + supported);
> +
> + unsupp = linkmode_andnot(tmp, edata->advertised, supported);
nit: Given the types involved, I might have written this as:
unsupp = !!linkmode_andnot(tmp, edata->advertised, supported);
> + if (unsupp) {
> DP_VERBOSE(edev, QED_MSG_DEBUG,
> - "Invalid advertised capabilities %d\n",
> - edata->advertised_u32);
> + "Invalid advertised capabilities %*pb\n",
> + __ETHTOOL_LINK_MODE_MASK_NBITS, edata->advertised);
> return -EINVAL;
> }
>
> - if (edata->advertised_u32 & ADVERTISED_1000baseT_Full)
> + if (linkmode_test_bit(ETHTOOL_LINK_MODE_1000baseT_Full_BIT,
> + edata->advertised))
> params.eee.adv_caps = QED_EEE_1G_ADV;
> - if (edata->advertised_u32 & ADVERTISED_10000baseT_Full)
> - params.eee.adv_caps |= QED_EEE_10G_ADV;
> + if (linkmode_test_bit(ETHTOOL_LINK_MODE_10000baseT_Full_BIT,
> + edata->advertised))
> + params.eee.adv_caps = QED_EEE_10G_ADV;
> +
> params.eee.enable = edata->eee_enabled;
> params.eee.tx_lpi_enable = edata->tx_lpi_enabled;
> params.eee.tx_lpi_timer = edata->tx_lpi_timer;
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2024-02-20 12:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 17:06 [PATCH net-next v4 0/9] drivers: net: Convert EEE handling to use linkmode bitmaps Andrew Lunn
2024-02-18 17:06 ` [PATCH net-next v4 1/9] net: usb: r8152: Use linkmode helpers for EEE Andrew Lunn
2024-02-20 12:56 ` Simon Horman
2024-02-18 17:06 ` [PATCH net-next v4 2/9] net: usb: ax88179_178a: " Andrew Lunn
2024-02-20 12:39 ` Simon Horman
2024-02-20 14:40 ` Andrew Lunn
2024-02-18 17:07 ` [PATCH net-next v4 3/9] net: qlogic: qede: " Andrew Lunn
2024-02-20 12:44 ` Simon Horman [this message]
2024-02-20 14:45 ` Andrew Lunn
2024-02-21 10:28 ` Simon Horman
2024-02-22 15:11 ` Andrew Lunn
2024-02-18 17:07 ` [PATCH net-next v4 4/9] net: ethernet: ixgbe: Convert EEE to use linkmodes Andrew Lunn
2024-02-20 12:06 ` Simon Horman
2024-02-20 14:47 ` Andrew Lunn
2024-02-18 17:07 ` [PATCH net-next v4 5/9] net: intel: i40e/igc: Remove setting Autoneg in EEE capabilities Andrew Lunn
2024-02-18 17:07 ` [PATCH net-next v4 6/9] net: intel: e1000e: Use linkmode helpers for EEE Andrew Lunn
2024-02-20 12:44 ` Simon Horman
2024-02-18 17:07 ` [PATCH net-next v4 7/9] net: intel: igb: " Andrew Lunn
2024-02-20 12:45 ` Simon Horman
2024-02-18 17:07 ` [PATCH net-next v4 8/9] net: intel: igc: " Andrew Lunn
2024-02-20 12:45 ` Simon Horman
2024-02-18 17:07 ` [PATCH net-next v4 9/9] net: ethtool: eee: Remove legacy _u32 from keee Andrew Lunn
2024-02-20 12:47 ` Simon Horman
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=20240220124405.GB40273@kernel.org \
--to=horms@kernel.org \
--cc=aelior@marvell.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manishc@marvell.com \
--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).