netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Wojciech Drewek <wojciech.drewek@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	przemyslaw.kitszel@intel.com
Subject: Re: [PATCH iwl-next v2] ice: Disable Cage Max Power override
Date: Thu, 24 Aug 2023 08:32:01 -0700	[thread overview]
Message-ID: <20230824083201.79f79513@kernel.org> (raw)
In-Reply-To: <20230824085459.35998-1-wojciech.drewek@intel.com>

On Thu, 24 Aug 2023 10:54:59 +0200 Wojciech Drewek wrote:
> NVM module called "Cage Max Power override" allows to
> change max power in the cage. This can be achieved
> using external tools. The responsibility of the ice driver is to
> go back to the default settings whenever port split is done.
> This is achieved by clearing Override Enable bit in the
> NVM module. Override of the max power is disabled so the
> default value will be used.

Can you say more? We have ETHTOOL_MSG_MODULE_GET / SET, sounds like
something we could quite easily get ethtool to support?

  parent reply	other threads:[~2023-08-24 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  8:54 [PATCH iwl-next v2] ice: Disable Cage Max Power override Wojciech Drewek
2023-08-24  9:38 ` Przemek Kitszel
2023-08-24 15:32 ` Jakub Kicinski [this message]
2023-08-25 11:01   ` Drewek, Wojciech
2023-08-26  0:54     ` Jakub Kicinski
2023-08-27  8:47     ` Ido Schimmel
2023-08-29  9:12       ` Drewek, Wojciech
2023-08-30 15:17         ` Ido Schimmel
2023-09-01 13:34           ` Drewek, Wojciech
2023-09-12 14:26             ` Ido Schimmel
2023-09-15 13:15               ` Drewek, Wojciech
2023-09-21 12:09                 ` Ido Schimmel
2023-10-05 13:58                   ` [Intel-wired-lan] " Drewek, Wojciech

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=20230824083201.79f79513@kernel.org \
    --to=kuba@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=wojciech.drewek@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;
as well as URLs for NNTP newsgroup(s).