From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net v1] ice: ethtool: advertise 1000M speeds properly
Date: Fri, 17 Jun 2022 10:03:03 +0200 [thread overview]
Message-ID: <2c962740-4941-cd4f-4528-3d2465ad50e1@molgen.mpg.de> (raw)
In-Reply-To: <20220607065556.3192203-1-anatolii.gerasymenko@intel.com>
Dear Anatolii,
Thank you for the patch.
Am 07.06.22 um 08:55 schrieb Anatolii Gerasymenko:
> In current implementation ice_update_phy_type enables all link modes
> for selected speed. This approach doesn't work for 1000M speeds,
> because both copper (1000baseT) and optical (1000baseX) standards
> cannot be enabled at once.
Is some error shown? What is the behavior of the system? I wonder why
this has gone unnoticed for such a long time.
> Add a special treatment for 1000M speeds.
Fix this, by adding the function `ice_set_phy_type_from_speed()` for
1000M speeds.
>
> Fixes: 48cb27f2fd18 ("ice: Implement handlers for ethtool PHY/link operations")
> Signed-off-by: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 39 +++++++++++++++++++-
> 1 file changed, 38 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_ethtool.c b/drivers/net/ethernet/intel/ice/ice_ethtool.c
> index 1e71b70f0e52..e3080c564432 100644
> --- a/drivers/net/ethernet/intel/ice/ice_ethtool.c
> +++ b/drivers/net/ethernet/intel/ice/ice_ethtool.c
> @@ -2189,6 +2189,42 @@ ice_setup_autoneg(struct ice_port_info *p, struct ethtool_link_ksettings *ks,
> return err;
> }
>
> +/**
> + * ice_set_phy_type_from_speed - set phy_types based on speeds
> + * and advertised modes
> + * @ks: ethtool link ksettings struct
> + * @phy_type_low: pointer to the lower part of phy_type
> + * @phy_type_high: pointer to the higher part of phy_type
> + * @adv_link_speed: targeted link speeds bitmap
> + */
> +static void
> +ice_set_phy_type_from_speed(const struct ethtool_link_ksettings *ks,
> + u64 *phy_type_low, u64 *phy_type_high,
> + u16 adv_link_speed)
> +{
> + /* Handle 1000M speed in a special way because ice_update_phy_type
> + * enables all link modes, but having mixed copper and optic standards
opitic*al*?
> + * is not supported
Add a dot/period at the end?
> + */
> + adv_link_speed &= ~ICE_AQ_LINK_SPEED_1000MB;
> +
> + if (ethtool_link_ksettings_test_link_mode(ks, advertising,
> + 1000baseT_Full))
> + *phy_type_low |= ICE_PHY_TYPE_LOW_1000BASE_T |
> + ICE_PHY_TYPE_LOW_1G_SGMII;
> +
> + if (ethtool_link_ksettings_test_link_mode(ks, advertising,
> + 1000baseKX_Full))
> + *phy_type_low |= ICE_PHY_TYPE_LOW_1000BASE_KX;
> +
> + if (ethtool_link_ksettings_test_link_mode(ks, advertising,
> + 1000baseX_Full))
> + *phy_type_low |= ICE_PHY_TYPE_LOW_1000BASE_SX |
> + ICE_PHY_TYPE_LOW_1000BASE_LX;
Make the second and third branch all else-if, and add an error, when all
there checks fail?
> +
> + ice_update_phy_type(phy_type_low, phy_type_high, adv_link_speed);
> +}
> +
> /**
> * ice_set_link_ksettings - Set Speed and Duplex
> * @netdev: network interface device structure
> @@ -2320,7 +2356,8 @@ ice_set_link_ksettings(struct net_device *netdev,
> adv_link_speed = curr_link_speed;
>
> /* Convert the advertise link speeds to their corresponded PHY_TYPE */
> - ice_update_phy_type(&phy_type_low, &phy_type_high, adv_link_speed);
> + ice_set_phy_type_from_speed(ks, &phy_type_low, &phy_type_high,
> + adv_link_speed);
>
> if (!autoneg_changed && adv_link_speed == curr_link_speed) {
> netdev_info(netdev, "Nothing changed, exiting without setting anything.\n");
Kind regards,
Paul
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-06-17 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 6:55 [Intel-wired-lan] [PATCH net v1] ice: ethtool: advertise 1000M speeds properly Anatolii Gerasymenko
2022-06-17 6:09 ` G, GurucharanX
2022-06-17 8:03 ` Paul Menzel [this message]
2022-06-20 7:46 ` Anatolii Gerasymenko
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=2c962740-4941-cd4f-4528-3d2465ad50e1@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=anatolii.gerasymenko@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
/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).