public inbox for intel-wired-lan@osuosl.org
 help / color / mirror / Atom feed
From: "Dahan, AvigailX" <avigailx.dahan@intel.com>
To: Vitaly Lifshits <vitaly.lifshits@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: <marmarek@invisiblethingslab.com>, <timo.teras@iki.fi>,
	<jeremie.wenger@edu.ge.ch>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v2 1/1] e1000e: reconfigure PLL clock gate value and re-enable K1 on Meteor Lake
Date: Tue, 10 Feb 2026 12:57:42 +0200	[thread overview]
Message-ID: <d390bfa3-9641-4e15-b1fc-04033a2c4d0c@intel.com> (raw)
In-Reply-To: <20260202103257.1972097-1-vitaly.lifshits@intel.com>



On 02/02/2026 12:32, Vitaly Lifshits wrote:
> Commit 3c7bf5af21960 ("e1000e: Introduce private flag to disable K1")
> disabled K1 by default on Meteor Lake and newer systems due to packet
> loss observed on various platforms. However, disabling K1 caused an
> increase in power consumption due to blocking PC10 state.
> 
> To mitigate this, reconfigure the PLL clock gate value so that K1 can
> remain enabled without incurring the additional power consumption.
> 
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=220954
> Fixes: 3c7bf5af21960 ("e1000e: Introduce private flag to disable K1")
> Signed-off-by: Vitaly Lifshits <vitaly.lifshits@intel.com>
> ---
> v2: add comment for the PLL timeout value and revisit the commit message
> v1: initial version
> ---
>   drivers/net/ethernet/intel/e1000e/ich8lan.c | 6 ++++++
>   drivers/net/ethernet/intel/e1000e/netdev.c  | 3 ---
>   2 files changed, 6 insertions(+), 3 deletions(-)
> 

Tested-by: Avigail Dahan <avigailx.dahan@intel.com>

  parent reply	other threads:[~2026-02-10 10:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 10:32 [Intel-wired-lan] [PATCH iwl-net v2 1/1] e1000e: reconfigure PLL clock gate value and re-enable K1 on Meteor Lake Vitaly Lifshits
2026-02-02 12:09 ` Loktionov, Aleksandr
2026-02-10 10:57 ` Dahan, AvigailX [this message]
2026-02-10 11:11 ` Timo Teras
2026-02-11 13:11   ` Ruinskiy, Dima
2026-02-12  9:15     ` Timo Teras
2026-02-22 16:05       ` Ruinskiy, Dima
2026-02-26 12:36         ` Timo Teras
2026-03-25 15:49           ` Ruinskiy, Dima
2026-04-01  7:07             ` Ruinskiy, Dima
2026-04-01  7:25               ` Timo Teras
2026-04-01  8:19                 ` Ruinskiy, Dima
2026-04-19  5:54                   ` Ruinskiy, Dima

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=d390bfa3-9641-4e15-b1fc-04033a2c4d0c@intel.com \
    --to=avigailx.dahan@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeremie.wenger@edu.ge.ch \
    --cc=marmarek@invisiblethingslab.com \
    --cc=timo.teras@iki.fi \
    --cc=vitaly.lifshits@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