From: Daniel Walker <dwalker@codeaurora.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>, San Mehat <san@google.com>,
Dmitry Shmidt <dimitrysh@google.com>,
Roel Kluin <roel.kluin@gmail.com>,
linux-arm-msm@vger.kernel.org
Subject: [GIT PULL] MSM mmc_sdcc driver update
Date: Tue, 18 May 2010 11:36:03 -0700 [thread overview]
Message-ID: <1274207763.29811.45.camel@c-dwalke-linux.qualcomm.com> (raw)
Some general fixes and updates. It's really more of a re-sync with the
current Google driver.
The following changes since commit 6b7b284958d47b77d06745b36bc7f36dab769d9b:
Linus Torvalds (1):
Linux 2.6.33-rc2
are available in the git repository at:
git://codeaurora.org/quic/kernel/dwalker/linux-msm.git msm-mmc_sdcc
Dmitry Shmidt (1):
mmc: msm_sdcc: Don't set host->curr.mrq until after we're sure the busclk timer won't fire
Roel Kluin (1):
msm_sdcc.c: missing brackets in msmsdcc_resume()
San Mehat (15):
mmc: msm_sdcc: Clean up clock management and add a 10us delay after enabling clocks
mmc: msm_sdcc: Snoop SDIO_CCCR_ABORT register
msm: Add 'execute' datamover callback
mmc: msm_sdcc: Driver clocking/irq improvements
mmc: msm_sdcc: Wrap readl/writel calls with appropriate clk delays
mmc: msm_sdcc: Schedule clock disable after probe
mmc: msm_sdcc: Reduce command timeouts and improve reliability.
mmc: msm_sdcc: Fix bug where busclk expiry timer was not properly disabled
mmc: msm_sdcc: Featurize busclock power save and disable it by default
mmc: msm_sdcc: Fix issue where we might not end a sucessfull request
mmc: msm_sdcc: Don't disable interrupts while suspending
mmc: msm_sdcc: Enable busclk idle timer for power savings
mmc: msm_sdcc: Fix the dma exec function to use the proper delays
mmc: msm_sdcc: Fix issue where clocks could be disabled mid transaction
drivers: mmc: msm_sdcc: Add EMBEDDED_SDIO support
arch/arm/mach-msm/dma.c | 5 +
arch/arm/mach-msm/include/mach/dma.h | 2 +
drivers/mmc/host/msm_sdcc.c | 476 ++++++++++++++++++++-------------
drivers/mmc/host/msm_sdcc.h | 15 +-
4 files changed, 309 insertions(+), 189 deletions(-)
reply other threads:[~2010-05-18 18:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1274207763.29811.45.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=dimitrysh@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=san@google.com \
--cc=torvalds@linux-foundation.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).