Re: [Intel-wired-lan] [PATCH iwl-net v2 1/1] e1000e: reconfigure PLL clock gate value and re-enable K1 on Meteor Lake

["Ruinskiy, Dima" <dima.ruinskiy@intel.com>]

On 25/03/2026 17:49, Ruinskiy, Dima wrote:
> On 26/02/2026 14:36, Timo Teras wrote:
>> Yes, generally maintaining a large quirk set is infeasible.
>>
>> But this is my point: if the affected set of machines with this issue
>> is so large that maintaining a quirk set becomes infeasible, then
>> the proposed change will make life very difficult for large enough
>> set of people that a better solution should be devised.
>>
>> Timo
>>
>>
> At this point, with the current PLL change, it looks like the number of 
> affected systems would be smaller than would be with the previous PLL 
> value.
> 
> So far we have not received additional reports of regressions caused by 
> this patch, other than yours. So, perhaps, the it can be manageable with 
> a DMI quirk approach. I went ahead and implemented the infrastructure, 
> it's actually quite a small change, and does what I want (automatically 
> alters the default value of the K1 disable flag).
> 
> Could you share the DMI IDs of your system, where the issue is observed? 
> Most likely the sys_vendor, product_family and product_name, located 
> under /sys/class/dmi/id would be the most useful. I can add them as an 
> initial DMI table entry for v3 of this patch (or a follow-up patch).
> 
> Thanks!
> --Dima
Hi Timo,

Just double-checking as a follow-up to my email last week.

We plan to send this patch upstream shortly, since the current situation 
where the upstream kernel is unable to pass Energy Star certification 
with the default settings is not acceptable.

If you want to share the DMI IDs of the problematic system I will go 
ahead and add those in v3 or in a follow-up patch, so that K1 is 
automatically disabled on that class of systems.

Thanks!
--Dima