Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dahan, AvigailX" <avigailx.dahan@intel.com>
To: Sasha Neftin <sasha.neftin@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [iwl-next v1 1/1] igc: Add Energy Efficient Ethernet ability
Date: Thu, 22 Aug 2024 16:28:17 +0300	[thread overview]
Message-ID: <d1f5b788-425b-8554-8ce0-32e2ec901189@intel.com> (raw)
In-Reply-To: <20240713190209.3742789-1-sasha.neftin@intel.com>

On 7/13/2024 10:02 PM, Sasha Neftin wrote:
> According to the IEEE standard report the EEE ability (registers 7.60 and
> 7.62) and the EEE Link Partner ability (registers 7.61 and 7.63). Use the
> kernel's 'ethtool_keee' structure and report EEE link modes.
> 
> Example:
> ethtool --show-eee <device>
> 
> Before:
> Advertised EEE link modes:  Not reported
> Link partner advertised EEE link modes:  Not reported
> 
> After:
> 	Advertised EEE link modes:  100baseT/Full
> 	                            1000baseT/Full
> 	                            2500baseT/Full
> 	Link partner advertised EEE link modes:  100baseT/Full
> 	                                         1000baseT/Full
> 	                                         2500baseT/Full
> 
> Signed-off-by: Sasha Neftin <sasha.neftin@intel.com>
> ---
>   drivers/net/ethernet/intel/igc/igc_defines.h | 10 +++
>   drivers/net/ethernet/intel/igc/igc_ethtool.c | 73 +++++++++++++++++++-
>   drivers/net/ethernet/intel/igc/igc_regs.h    |  7 ++
>   3 files changed, 89 insertions(+), 1 deletion(-)
> 
Tested-by: Avigail Dahan <avigailx.dahan@intel.com>

      reply	other threads:[~2024-08-22 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 19:02 [Intel-wired-lan] [iwl-next v1 1/1] igc: Add Energy Efficient Ethernet ability Sasha Neftin
2024-08-22 13:28 ` Dahan, AvigailX [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=d1f5b788-425b-8554-8ce0-32e2ec901189@intel.com \
    --to=avigailx.dahan@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=sasha.neftin@intel.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