From: David Vrabel <david.vrabel@csr.com>
To: linux-mmc@vger.kernel.org
Cc: linux-omap@vger.kernel.org, madhu.cr@ti.com,
David Vrabel <david.vrabel@csr.com>
Subject: [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2)
Date: Mon, 22 Feb 2010 14:24:17 +0000 [thread overview]
Message-ID: <cover.1266847842.git.david.vrabel@csr.com> (raw)
These patches add support for SDIO cards to the omap_hsmmc driver.
Power management changes to prevent SDIO cards from being turned off
and losing all state, and card interrupts.
I've been unable to test these exact patches as I only have an N900 for
testing and the N900 support in mainline is incomplete.
Changes since v1:
- (hopefully) get all cards working again by removing a second call to
read MMCi_STAT in the interrupt handler.
- flush posted writes after enabling/disabling SDIO interrupts.
- tweak the FIXME commit on disabling FCLK to better match what really
going on (at least I think so anyway).
David Vrabel (2):
mmc: omap_hsmmc: don't turn SDIO cards off when idle
mmc: omap_hsmmc: enable SDIO card interrupts
drivers/mmc/host/omap_hsmmc.c | 114 ++++++++++++++++++++++++++++-------------
1 files changed, 79 insertions(+), 35 deletions(-)
next reply other threads:[~2010-02-22 14:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 14:24 David Vrabel [this message]
2010-02-22 14:24 ` [PATCH 1/2] mmc: omap_hsmmc: don't turn SDIO cards off when idle David Vrabel
2010-02-22 14:24 ` [PATCH 2/2] mmc: omap_hsmmc: enable SDIO card interrupts David Vrabel
2010-02-22 14:55 ` [PATCH 0/2] mmc: omap_hsmmc: support SDIO cards (#2) Felipe Contreras
2010-02-22 15:11 ` David Vrabel
2010-02-22 15:50 ` Felipe Contreras
2010-02-24 10:07 ` Mike Rapoport
2010-08-27 19:22 ` Chris Ball
2010-08-31 8:59 ` David Vrabel
2010-09-01 18:07 ` mike
2010-09-02 6:02 ` Mike Rapoport
2010-10-04 16:32 ` Steve Sakoman
2010-10-04 16:45 ` Madhusudhan
2010-10-04 16:57 ` Steve Sakoman
2010-10-04 17:33 ` Madhusudhan
2010-10-04 18:09 ` Steve Sakoman
2010-10-06 6:17 ` Mike Rapoport
2010-10-06 12:55 ` Steve Sakoman
2010-10-06 13:45 ` Mike Rapoport
2010-10-06 15:22 ` Steve Sakoman
2010-10-06 18:28 ` Madhusudhan Chikkature
2010-10-06 19:02 ` David Vrabel
2010-10-06 19:21 ` Madhusudhan
2010-10-07 7:15 ` Mike Rapoport
2010-10-07 13:56 ` Steve Sakoman
2010-10-07 16:52 ` Madhusudhan
2010-10-07 17:56 ` Steve Sakoman
2010-10-10 6:50 ` Mike Rapoport
2010-10-29 11:33 ` Enric Balletbò i Serra
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=cover.1266847842.git.david.vrabel@csr.com \
--to=david.vrabel@csr.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
/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).