From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Ian Molton <ian@mnementh.co.uk>,
linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD
Date: Mon, 21 Mar 2011 11:19:29 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1103211208290.21013@axis700.grange> (raw)
In-Reply-To: <AANLkTiksL=M0GOUy4-g7wiA6dj5TdW3atLNJiQ3zgien@mail.gmail.com>
Hi Ian
On Wed, 16 Mar 2011, Magnus Damm wrote:
> >>>> >> On Fri, Mar 11, 2011 at 4:51 PM, Guennadi Liakhovetski
> >>>> >> <g.liakhovetski@gmx.de> wrote:
> >>>> >> > TMIO MMC chips contain an SD / SDIO IP core from Panasonic, similar to
> >>>> >> > the one, used in MN5774 and other MN57xx controllers. These IP cores are
> >>>> >> > included in many multifunction devices, in sh-mobile chips from Renesas,
> >>>> >> > in the latter case they can also use DMA. Some sh-mobile implementations
> >>>> >> > also have some other specialities, that MFD-based solutions don't have.
> >>>> >> > This makes supporting all these features in a monolithic driver inconveniet
> >>>> >> > and error-prone. This patch splits the driver into 3 parts: the core,
> >>>> >> > the MFD glue and the DMA support. In case of a modular build, two modules
> >>>> >> > will be built: mmc_tmio_core and mmc_tmio.
> >>>> >> >
> >>>> >> > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>
> On Wed, Mar 16, 2011 at 8:09 PM, Ian Molton <ian@mnementh.co.uk> wrote:
> > Im fine with it as long as it doesnt complicate my plan to add PXA DMA
> > to the driver.
>
> Hi Ian,
>
> Thanks for your email. I'm glad to hear that you have no objections to
> this patch series.
>
> Regarding PXA DMA, without knowing the PXA DMA hardware that well
> (never recall using DMA on that platform), from a code reuse point of
> view it would be absolutely best to share the DMA Engine interface in
> the tmio mmc driver with the SDHI. But I'm not sure if any DMA Engine
> driver exists for the PXA though.
I presume you're talking about an external tmio MFD chip connected to a
PXA SoC. Concerning adding DMA to this configuration, just like Magnus, I
am not aware of any dmaengine implementations for PXA. I know, there is a
private PXA DMA API, used, e.g., in pxa_camera.c and defined in
arch/arm/plat-pxa/dma.c. I think, that's also what you would use for
external DMA.
There has been a discussion whether the dmaengine API should be used
universally, and the conclusion more or less was:
1. if your DMA engine can do standard operations like memcpy, xor, then
yes
2. if you use drivers for external hardware or built-in IP blocks, that
use the dmaengine API, then yes
3. otherwise it's not compulsory
So, until now PXA didn't have any of the (1) or (2) cases. Now, if you
want to use tmio on PXA you have a choice: either (1) to add a new DMA
glue to tmio for PXA, or (2) to add a dmaengine API to PXA DMA. The latter
seems to be preferred. But even if you decide to go the first route, this
driver split shall make your work easier.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2011-03-21 11:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 7:51 [PATCH 0/6] mmc: split the tmio driver into several modules Guennadi Liakhovetski
2011-03-11 7:51 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Guennadi Liakhovetski
2011-03-12 16:05 ` Magnus Damm
2011-03-12 22:48 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD Guennadi Liakhovetski
2011-03-13 3:57 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Magnus Damm
2011-03-13 22:51 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD Guennadi Liakhovetski
2011-03-15 9:01 ` [PATCH 1/6] mmc: tmio: split core functionality, DMA and MFD glue Magnus Damm
2011-03-16 11:09 ` Ian Molton
2011-03-16 12:37 ` Magnus Damm
2011-03-21 11:19 ` Guennadi Liakhovetski [this message]
2011-03-11 7:52 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead of Guennadi Liakhovetski
2011-03-12 16:18 ` [PATCH 2/6] sh: ecovec: use the CONFIG_MMC_TMIO symbols instead Magnus Damm
2011-03-12 23:00 ` Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a Guennadi Liakhovetski
2011-03-13 4:14 ` Magnus Damm
2011-03-14 8:01 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to Guennadi Liakhovetski
2011-03-15 9:09 ` [PATCH 3/6] mmc: tmio: convert the SDHI MMC driver from MFD to a Magnus Damm
2011-03-11 7:52 ` [PATCH 4/6] ARM: mach-shmobile: convert boards to use Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 5/6] sh: convert boards to use linux/mmc/sh_mobile_sdhi.h Guennadi Liakhovetski
2011-03-11 7:52 ` [PATCH 6/6] mfd: remove now redundant sh_mobile_sdhi.h header Guennadi Liakhovetski
2011-03-15 21:25 ` [PATCH 0/6] mmc: split the tmio driver into several modules Ian Molton
2011-03-21 11:38 ` Guennadi Liakhovetski
2011-03-22 5:31 ` Simon Horman
2011-03-22 12:28 ` Paul Mundt
2011-03-22 22:06 ` Simon Horman
2011-03-23 14:54 ` Paul Mundt
2011-03-23 22:42 ` Simon Horman
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=Pine.LNX.4.64.1103211208290.21013@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=cjb@laptop.org \
--cc=ian@mnementh.co.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).