Am Freitag 12 November 2010 schrieb Helmut Schaa: > Am Donnerstag 11 November 2010 schrieb Helmut Schaa: > > On Thu, Nov 11, 2010 at 3:56 PM, Tim Blechmann <tim@xxxxxxxxxx> wrote: > > >> Mind to put a (maybe rate limited) printk into the interrupt thread > > >> that prints out "reg" > > >> and "reg_mcu" so that we can see which interrupts get triggered? > > > > > > log attached, generated with: > > > > Thanks. Unfortunately nothing special in there. Mostly RX and TX interrupts. So > > there must be something else ... > > Tim, is this on x86 hw? Or something else? I don't know if this will do any good or harm but it could be worth a try as the spec for rt61pci says something like: "Don't enable interrupt mitigation in the same write as releasing the other masks.". Since we always write a mitigation period of 0xff == "No mitigation period" we can simply leave interrupt mitigation disabled. I really don't have any clue if this will fix anything but it might be worth a try. Thanks, Helmut diff --git a/drivers/net/wireless/rt2x00/rt61pci.c b/drivers/net/wireless/rt2x00/rt61pci.c index af548c8..fde8220 100644 --- a/drivers/net/wireless/rt2x00/rt61pci.c +++ b/drivers/net/wireless/rt2x00/rt61pci.c @@ -1655,8 +1655,6 @@ static void rt61pci_toggle_irq(struct rt2x00_dev *rt2x00dev, rt2x00_set_field32(®, INT_MASK_CSR_TXDONE, mask); rt2x00_set_field32(®, INT_MASK_CSR_RXDONE, mask); rt2x00_set_field32(®, INT_MASK_CSR_BEACON_DONE, mask); - rt2x00_set_field32(®, INT_MASK_CSR_ENABLE_MITIGATION, mask); - rt2x00_set_field32(®, INT_MASK_CSR_MITIGATION_PERIOD, 0xff); rt2x00pci_register_write(rt2x00dev, INT_MASK_CSR, reg); rt2x00pci_register_read(rt2x00dev, MCU_INT_MASK_CSR, ®); -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
