Date: Wed, 23 Nov 2011 03:57:44 -0500 (EST)
Message-Id: <20111123.035744.1607233076642546274.davem@davemloft.net> (sfid-20111123_095919_565551_A4AB84EB)
To: sgruszka@redhat.com
Cc: Larry.Finger@lwfinger.net, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, IvDoorn@gmail.com,
	gwingerde@gmail.com, helmut.schaa@googlemail.com,
	hedayaty@gmail.com
Subject: Re: pull request: wireless 2011-11-22
From: David Miller <davem@davemloft.net>
In-Reply-To: <20111123080353.GA3752@redhat.com>
References: <4ECC1479.8090209@lwfinger.net>
	<20111122.164057.1411098663938026383.davem@davemloft.net>
	<20111123080353.GA3752@redhat.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Sender: linux-wireless-owner@vger.kernel.org

From: Stanislaw Gruszka <sgruszka@redhat.com>
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.