From: per.forlin@stericsson.com (Per Forlin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] sdio: add quirk for spurious SDIO IRQ
Date: Wed, 1 Jun 2011 10:48:31 +0200 [thread overview]
Message-ID: <1306918113-23872-1-git-send-email-per.forlin@stericsson.com> (raw)
From: Per Forlin <per.forlin@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.
Changes since v1:
* Replace public sdio function to enable disable SDIO single IRQ function
with a quirk
Per Forlin (2):
sdio: add quirk to handle pending IRQ in case of none CCCR_INTx bits
sdio: report error if pending IRQ but none CCCR_INTx bits
drivers/mmc/core/sdio_irq.c | 9 +++++++--
include/linux/mmc/card.h | 1 +
2 files changed, 8 insertions(+), 2 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-06-01 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 8:48 Per Forlin [this message]
2011-06-01 8:48 ` [PATCH v2 1/2] sdio: add quirk to handle pending IRQ in case of none CCCR_INTx bits Per Forlin
2011-06-01 8:48 ` [PATCH v2 2/2] sdio: report error if pending IRQ but " Per Forlin
2011-06-01 21:36 ` [PATCH v2 1/2] sdio: add quirk to handle pending IRQ in case of " Troy Kisky
2011-06-07 6:49 ` Per Forlin
2011-06-01 15:59 ` [PATCH v2 0/2] sdio: add quirk for spurious SDIO IRQ Nicolas Pitre
2011-06-01 17:00 ` Chris Ball
2011-06-07 6:41 ` Per Forlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306918113-23872-1-git-send-email-per.forlin@stericsson.com \
--to=per.forlin@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).