Commit b5fc8f0c authored by Jesse Brandeburg's avatar Jesse Brandeburg Committed by Jeff Garzik

e1000: Fix MSI only interrupt handler routine

Unfortunately the read-free MSI interrupt handler needs to flush write
the icr register and thus we can't be read-free. Our MSI irq routine
thus becomes a lot more simpler since we don't need to track link state
anymore.
Signed-off-by: default avatarJesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: default avatarAuke Kok <auke-jan.h.kok@intel.com>
parent bf3cea4d
...@@ -257,7 +257,6 @@ struct e1000_adapter { ...@@ -257,7 +257,6 @@ struct e1000_adapter {
spinlock_t tx_queue_lock; spinlock_t tx_queue_lock;
#endif #endif
atomic_t irq_sem; atomic_t irq_sem;
unsigned int detect_link;
unsigned int total_tx_bytes; unsigned int total_tx_bytes;
unsigned int total_tx_packets; unsigned int total_tx_packets;
unsigned int total_rx_bytes; unsigned int total_rx_bytes;
......
...@@ -3765,8 +3765,8 @@ e1000_update_stats(struct e1000_adapter *adapter) ...@@ -3765,8 +3765,8 @@ e1000_update_stats(struct e1000_adapter *adapter)
* @data: pointer to a network interface device structure * @data: pointer to a network interface device structure
**/ **/
static static irqreturn_t
irqreturn_t e1000_intr_msi(int irq, void *data) e1000_intr_msi(int irq, void *data)
{ {
struct net_device *netdev = data; struct net_device *netdev = data;
struct e1000_adapter *adapter = netdev_priv(netdev); struct e1000_adapter *adapter = netdev_priv(netdev);
...@@ -3774,49 +3774,27 @@ irqreturn_t e1000_intr_msi(int irq, void *data) ...@@ -3774,49 +3774,27 @@ irqreturn_t e1000_intr_msi(int irq, void *data)
#ifndef CONFIG_E1000_NAPI #ifndef CONFIG_E1000_NAPI
int i; int i;
#endif #endif
uint32_t icr = E1000_READ_REG(hw, ICR);
/* this code avoids the read of ICR but has to get 1000 interrupts
* at every link change event before it will notice the change */
if (++adapter->detect_link >= 1000) {
uint32_t icr = E1000_READ_REG(hw, ICR);
#ifdef CONFIG_E1000_NAPI #ifdef CONFIG_E1000_NAPI
/* read ICR disables interrupts using IAM, so keep up with our /* read ICR disables interrupts using IAM, so keep up with our
* enable/disable accounting */ * enable/disable accounting */
atomic_inc(&adapter->irq_sem); atomic_inc(&adapter->irq_sem);
#endif #endif
adapter->detect_link = 0; if (icr & (E1000_ICR_RXSEQ | E1000_ICR_LSC)) {
if ((icr & (E1000_ICR_RXSEQ | E1000_ICR_LSC)) && hw->get_link_status = 1;
(icr & E1000_ICR_INT_ASSERTED)) { /* 80003ES2LAN workaround-- For packet buffer work-around on
hw->get_link_status = 1; * link down event; disable receives here in the ISR and reset
/* 80003ES2LAN workaround-- * adapter in watchdog */
* For packet buffer work-around on link down event; if (netif_carrier_ok(netdev) &&
* disable receives here in the ISR and (adapter->hw.mac_type == e1000_80003es2lan)) {
* reset adapter in watchdog /* disable receives */
*/ uint32_t rctl = E1000_READ_REG(hw, RCTL);
if (netif_carrier_ok(netdev) && E1000_WRITE_REG(hw, RCTL, rctl & ~E1000_RCTL_EN);
(adapter->hw.mac_type == e1000_80003es2lan)) {
/* disable receives */
uint32_t rctl = E1000_READ_REG(hw, RCTL);
E1000_WRITE_REG(hw, RCTL, rctl & ~E1000_RCTL_EN);
}
/* guard against interrupt when we're going down */
if (!test_bit(__E1000_DOWN, &adapter->flags))
mod_timer(&adapter->watchdog_timer,
jiffies + 1);
} }
} else { /* guard against interrupt when we're going down */
E1000_WRITE_REG(hw, ICR, (0xffffffff & ~(E1000_ICR_RXSEQ | if (!test_bit(__E1000_DOWN, &adapter->flags))
E1000_ICR_LSC))); mod_timer(&adapter->watchdog_timer, jiffies + 1);
/* bummer we have to flush here, but things break otherwise as
* some event appears to be lost or delayed and throughput
* drops. In almost all tests this flush is un-necessary */
E1000_WRITE_FLUSH(hw);
#ifdef CONFIG_E1000_NAPI
/* Interrupt Auto-Mask (IAM)...upon writing ICR, interrupts are
* masked. No need for the IMC write, but it does mean we
* should account for it ASAP. */
atomic_inc(&adapter->irq_sem);
#endif
} }
#ifdef CONFIG_E1000_NAPI #ifdef CONFIG_E1000_NAPI
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment