[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08bfd370e195b648b9cb4a9d9e31fb4189a374c1.camel@intel.com>
Date: Tue, 23 Jul 2019 19:30:21 -0700
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
To: David Miller <davem@...emloft.net>
Cc: kai.heng.feng@...onical.com, netdev@...r.kernel.org,
nhorman@...hat.com, sassmann@...hat.com, aaron.f.brown@...el.com
Subject: Re: [net-next 6/6] e1000e: disable force K1-off feature
On Tue, 2019-07-23 at 14:04 -0700, David Miller wrote:
> From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
> Date: Tue, 23 Jul 2019 10:36:50 -0700
>
> > diff --git a/drivers/net/ethernet/intel/e1000e/hw.h
> > b/drivers/net/ethernet/intel/e1000e/hw.h
> > index eff75bd8a8f0..e3c71fd093ee 100644
> > --- a/drivers/net/ethernet/intel/e1000e/hw.h
> > +++ b/drivers/net/ethernet/intel/e1000e/hw.h
> > @@ -662,6 +662,7 @@ struct e1000_dev_spec_ich8lan {
> > bool kmrn_lock_loss_workaround_enabled;
> > struct e1000_shadow_ram shadow_ram[E1000_ICH8_SHADOW_RAM_WORDS];
> > bool nvm_k1_enabled;
> > + bool disable_k1_off;
> > bool eee_disable;
>
> I don't see any code actually setting this boolean, how does it work?
I am trying to find the answer Dave. The original author of the code
change is no longer with Intel and the notes point to this being set via
the NVM, but I am confirming with the client engineers.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists