From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: LPC32xx and MMCI driver
Date: Thu, 20 Dec 2012 11:43:08 +0100 [thread overview]
Message-ID: <50D2EBBC.2070803@antcom.de> (raw)
In-Reply-To: <50D2E317.6000005@precidata.com>
Hi,
On 12/20/2012 11:06 AM, Gabriele Mondada wrote:
> Hi,
> Currently, LPC32xx plateform do not enable DMA on the mmci driver. This
> makes the driver useless because getting out data from a 64 bytes FIFO
> by interrupt is not fast enough (at standard SD-card data rate).
>
> DMA is not enabled because LPC32xx has a bug that prevent DMA to work
> properly with the MMC controller (silicon bug, I guess). NXP did a patch
> to workaround this, but it has not been commited on the main branch. The
> patch is for linux 2.6.39.2 and does not use dmaengine.
>
> So, I reworked this patch to make it compatible with the last kernel
> (3.7). Here it is. Have I any chance to see this patch be commited on
> the main branch?
First, thank you for the patch!
Unfortunately, it doesn't apply to v3.7 in the form it arrived in my
INBOX (mainly formatting issues, maybe MUA related?). Can you please
check and resend? I'd like to test it.
Further, there seem to be many #ifdefs in two subsystems (mmc and dma)
at once. First, maybe the LPC32XX specific pl08x_force_dma_burst() could
be moved to mmci.c since it is only used there and this would minimize
the patch to only the mmc subsystem.
And maybe at least some of the ifdefs could be removed.
The less ifdefs, the higher the chances of mainlining. ;-)
Thanks in advance,
Roland
next prev parent reply other threads:[~2012-12-20 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D2E156.20707@precidata.com>
2012-12-20 10:06 ` LPC32xx and MMCI driver Gabriele Mondada
2012-12-20 10:43 ` Roland Stigge [this message]
2012-12-22 21:24 ` Russell King - ARM Linux
2013-01-23 10:32 ` Gabriele Mondada
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=50D2EBBC.2070803@antcom.de \
--to=stigge@antcom.de \
--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