...@linutronix.de; linux-ker...@vger.kernel.org;
> eduma...@google.com; Nguyen, Anthony L ; Kitszel,
> Przemyslaw ; k...@kernel.org;
> pab...@redhat.com; da...@davemloft.net
> Subject: [Intel-wired-lan] [PATCH iwl-net v3] igb: Fix not clearing TimeSync
> interrupts for 82580
>
&
On Tue Aug 13 2024, Daiwei Li wrote:
> 82580 NICs have a hardware bug that makes it
> necessary to write into the TSICR (TimeSync Interrupt Cause) register
> to clear it:
> https://lore.kernel.org/all/cdcb8be0.1ec2c%25matthew.v...@intel.com/
>
> Add a conditional so only for 82580 we write into the
Daiwei Li writes:
> 82580 NICs have a hardware bug that makes it
> necessary to write into the TSICR (TimeSync Interrupt Cause) register
> to clear it:
> https://lore.kernel.org/all/cdcb8be0.1ec2c%25matthew.v...@intel.com/
>
> Add a conditional so only for 82580 we write into the TSICR register,
82580 NICs have a hardware bug that makes it
necessary to write into the TSICR (TimeSync Interrupt Cause) register
to clear it:
https://lore.kernel.org/all/cdcb8be0.1ec2c%25matthew.v...@intel.com/
Add a conditional so only for 82580 we write into the TSICR register,
so we don't risk losing events
On Tue, Aug 13, 2024 at 09:55:53PM -0700, Daiwei Li wrote:
> 82580 NICs have a hardware bug that makes it
> necessary to write into the TSICR (TimeSync Interrupt Cause) register
> to clear it:
> https://lore.kernel.org/all/cdcb8be0.1ec2c%25matthew.v...@intel.com/
>
> Add a conditional so only for
