On 1 June 2011 17:59, Nicolas Pitre <nicolas.pi...@linaro.org> wrote: > On Wed, 1 Jun 2011, Per Forlin wrote: > >> From: Per Forlin <per.for...@linaro.org> >> >> Daniel Drake reported an issue in the libertas sdio client that was >> triggered by the sdio_single_irq functionality. His SDIO device seems to >> raise an interrupt even though there are no bits set in the CCCR_INTx >> register. This behaviour is not supported by the sdio_single_irq feature nor >> the SDIO spec. The purpose of the sdio_single_irq feature is to avoid the >> overhead of checking the CCCR_INTx registers, this result in no error >> handling of the case if there is a pending IRQ with none CCCR_INTx bits set. >> >> This patchset adds a quirk to support this spurious IRQ issue and also report >> a warning if an SDIO interrupt is raised but none CCCR_INTx bits are set. > > Given that the issue can be fixed locally to the libertas driver, I'd > suggest not merging this series until truly unfixable issues come up, as > Daniel said. > I agree too.
Thanks, Per -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
