From: cjb@laptop.org (Chris Ball)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] mmc: atmel-mci: AP700x PDC is not connected to MCI
Date: Wed, 19 Sep 2012 01:21:31 -0400 [thread overview]
Message-ID: <m3d31ik2p0.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <503F9613.5060007@yahoo.es> (Hein Tibosch's message of "Fri, 31 Aug 2012 00:34:27 +0800")
Hi,
On Thu, Aug 30 2012, Hein Tibosch wrote:
> Earlier, atmel-mci was adapted to make use of the peripheral DMA
> controller (PDC), in case normal DMA wouldn't work.
> ( http://comments.gmane.org/gmane.linux.kernel.mmc/9403 )
> This works OK on ARM platforms (AT91), but it broke the driver
> for AVR32, the AP700x.
> Although the MCI has PDC support, the connection is not done for
> AVR chips
>
> This patch makes the use of PDC depend on CONFIG_AVR32
>
> Signed-off-by: Hein Tibosch <hein_tibosch@yahoo.es>
>
> ---
> drivers/mmc/host/atmel-mci-regs.h | 7 +++++++
> drivers/mmc/host/atmel-mci.c | 2 +-
> 2 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mmc/host/atmel-mci-regs.h b/drivers/mmc/host/atmel-mci-regs.h
> index ab56f7d..c97001e 100644
> --- a/drivers/mmc/host/atmel-mci-regs.h
> +++ b/drivers/mmc/host/atmel-mci-regs.h
> @@ -140,6 +140,13 @@
> #define atmci_writel(port,reg,value) \
> __raw_writel((value), (port)->regs + reg)
>
> +/* On AVR chips the Peripheral DMA Controller is not connected to MCI. */
> +#ifdef CONFIG_AVR32
> +# define ATMCI_PDC_CONNECTED 0
> +#else
> +# define ATMCI_PDC_CONNECTED 1
> +#endif
> +
> /*
> * Fix sconfig's burst size according to atmel MCI. We need to convert them as:
> * 1 -> 0, 4 -> 1, 8 -> 2, 16 -> 3.
> diff --git a/drivers/mmc/host/atmel-mci.c b/drivers/mmc/host/atmel-mci.c
> index a6a5593..b8de891 100644
> --- a/drivers/mmc/host/atmel-mci.c
> +++ b/drivers/mmc/host/atmel-mci.c
> @@ -2208,7 +2208,7 @@ static void __init atmci_get_cap(struct atmel_mci *host)
> "version: 0x%x\n", version);
>
> host->caps.has_dma_conf_reg = 0;
> - host->caps.has_pdc = 1;
> + host->caps.has_pdc = ATMCI_PDC_CONNECTED;
> host->caps.has_cfg_reg = 0;
> host->caps.has_cstor_reg = 0;
> host->caps.has_highspeed = 0;
Thanks, pushed to mmc-next for 3.7.
I changed the commit message text to reflect my understanding of what
the patch does better, from:
This patch makes the use of PDC depend on CONFIG_AVR32.
to:
This patch makes the use of PDC depend on !CONFIG_AVR32.
(Ludovic, perhaps you could give an ACK for this patch?)
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-09-19 5:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 16:34 [PATCH v2 2/2] mmc: atmel-mci: AP700x PDC is not connected to MCI Hein Tibosch
2012-09-19 5:21 ` Chris Ball [this message]
2012-09-19 6:59 ` ludovic.desroches
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=m3d31ik2p0.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--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).