Re: pull request: wireless 2011-11-22

[David Miller]

From: Stanislaw Gruszka <sgruszka@xxxxxxxxxx>
Date: Wed, 23 Nov 2011 09:03:54 +0100

> The main problem here, that we have hardware (or firmware) that
> generate interrupt with empty interrupt status register, so we can
> not detect if interrupt is really generated by Ralink device.
> 
> Perhaps exist good fix for that problem, i.e. we can write to some
> register to stop hardware generating spurious interrupts, or exist
> other way than reading status register to find out if Ralink device
> generated interrupt. But that require detailed hardware knowledge,
> and I'm not sure if we ever can get such informations. Also this 
> could be a hardware bug, device just generate spurious interrupts
> and we can not do anything about it. I looked at driver from Ralink
> site, and it do exactly that, it return IRQ_HANDLED if status register
> is empty.

Then it is also buggy :-)

> Ok, I'm thinking about other fix now ...

Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/