From: Linus Walleij <linus.walleij@linaro.org>
To: Per Forlin <per.forlin@linaro.org>, Daniel Drake <dsd@laptop.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nicolas.pitre@linaro.org>,
linaro-dev@lists.linaro.org
Subject: Re: [PATCH 1/2] sdio: add function to enable and disable sdio_single_irq optimization
Date: Wed, 1 Jun 2011 09:30:58 +0200 [thread overview]
Message-ID: <BANLkTinUEq_tvCtXWjg3t6L589y80nPPog@mail.gmail.com> (raw)
In-Reply-To: <1306874008-28867-2-git-send-email-per.forlin@linaro.org>
2011/5/31 Per Forlin <per.forlin@linaro.org>:
> +/**
> + * sdio_single_irq_enable - enable or disable SDIO single IRQ function
> + * @card: card to enable SDIO single irq
> + * @value: true to enable SDIO single irq function, false to disable
> + *
> + * If there is only 1 function interrupt registered and SDIO single IRQ
> + * is enable, the irq handler is called directly without reading
> + * the CCCR registers
> + */
> +void sdio_single_irq_enable(struct mmc_card *card, bool value)
> +{
> + card->sdio_single_irq_en = value;
> +}
> +EXPORT_SYMBOL_GPL(sdio_single_irq_enable);
Can we use a quirk for implementing this for the specific problematic
card instead?
Daniel, do you have the vendor and device ID for the problematic
Libertas card you're working on so this can be quirked explicitly
in drivers/mmc/core/quirks.c?
Yours,
Linus Walleij
next prev parent reply other threads:[~2011-06-01 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 20:33 [PATCH 0/2] sdio: make sdio_single_irq optional due to suprious IRQ Per Forlin
2011-05-31 20:33 ` [PATCH 1/2] sdio: add function to enable and disable sdio_single_irq optimization Per Forlin
2011-06-01 7:30 ` Linus Walleij [this message]
2011-06-01 7:39 ` Per Forlin
2011-05-31 20:33 ` [PATCH 2/2] sdio: report error if pending IRQ but none function bits Per Forlin
2011-06-01 14:30 ` Nicolas Pitre
2011-06-07 7:02 ` Per Forlin
2011-05-31 21:52 ` [PATCH 0/2] sdio: make sdio_single_irq optional due to suprious IRQ Daniel Drake
2011-06-01 14:29 ` Nicolas Pitre
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=BANLkTinUEq_tvCtXWjg3t6L589y80nPPog@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=dsd@laptop.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=per.forlin@linaro.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).