Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-11-04 Thread Alexander Duyck
On 11/04/2015 03:19 PM, Benjamin Poirier wrote: On 2015/10/30 12:19, Alexander Duyck wrote: On 10/30/2015 10:31 AM, Benjamin Poirier wrote: Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574

Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-11-04 Thread Benjamin Poirier
On 2015/10/30 12:19, Alexander Duyck wrote: > On 10/30/2015 10:31 AM, Benjamin Poirier wrote: > >Using eiac instead of reading icr allows us to avoid interference with > >rx and tx interrupts in the Other interrupt handler. > > > >According to the 82574 datasheet section 10.2.4.1, interrupt causes

Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-11-04 Thread Benjamin Poirier
On 2015/10/30 12:19, Alexander Duyck wrote: > On 10/30/2015 10:31 AM, Benjamin Poirier wrote: > >Using eiac instead of reading icr allows us to avoid interference with > >rx and tx interrupts in the Other interrupt handler. > > > >According to the 82574 datasheet section 10.2.4.1, interrupt causes

Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-11-04 Thread Alexander Duyck
On 11/04/2015 03:19 PM, Benjamin Poirier wrote: On 2015/10/30 12:19, Alexander Duyck wrote: On 10/30/2015 10:31 AM, Benjamin Poirier wrote: Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574

Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-10-30 Thread Alexander Duyck
On 10/30/2015 10:31 AM, Benjamin Poirier wrote: Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574 datasheet section 10.2.4.1, interrupt causes that trigger the Other interrupt are 1) Link Status

[PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-10-30 Thread Benjamin Poirier
Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574 datasheet section 10.2.4.1, interrupt causes that trigger the Other interrupt are 1) Link Status Change. 2) Receiver Overrun. 3) MDIO Access Complete.

Re: [PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-10-30 Thread Alexander Duyck
On 10/30/2015 10:31 AM, Benjamin Poirier wrote: Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574 datasheet section 10.2.4.1, interrupt causes that trigger the Other interrupt are 1) Link Status

[PATCH v2 2/4] e1000e: Do not read icr in Other interrupt

2015-10-30 Thread Benjamin Poirier
Using eiac instead of reading icr allows us to avoid interference with rx and tx interrupts in the Other interrupt handler. According to the 82574 datasheet section 10.2.4.1, interrupt causes that trigger the Other interrupt are 1) Link Status Change. 2) Receiver Overrun. 3) MDIO Access Complete.