From: Tony Lindgren <tony@atomide.com>
To: Kishore Kadiyala <kishore.kadiyala@ti.com>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
cjb@laptop.org, madhu.cr@ti.com
Subject: Re: [PATCH 0/4] omap4: hsmmc: Adding ADMA support
Date: Thu, 20 Jan 2011 09:42:27 -0800 [thread overview]
Message-ID: <20110120174226.GX4957@atomide.com> (raw)
In-Reply-To: <1295371591-13610-1-git-send-email-kishore.kadiyala@ti.com>
* Kishore Kadiyala <kishore.kadiyala@ti.com> [110118 09:19]:
> This patch series adds support for ADMA on MMC1 & MMC2 controllers on OMAP4.
> There is no performance improvement observed using ADMA over SDMA.
> Advantage using ADMA could be reducing contention over SDMA.
> Also the series includes some cleanup.
To me it seems that the only sane way to deal with multiple different
DMA enginges is to implement them all with drivers/dma/dmaengine.c.
Otherwise we'll end up with multiple custom ADMA implementations in
each driver. We need to also make SDMA use the dmaengine code.
If the current dmaengine code does not support this, we need to
improve it to deal with cases like these.
Regards,
Tony
next prev parent reply other threads:[~2011-01-20 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 17:26 [PATCH 0/4] omap4: hsmmc: Adding ADMA support Kishore Kadiyala
2011-01-18 17:26 ` [PATCH 1/4] omap: hsmmc: Rename use_dma to xfer_type and define possible transfers Kishore Kadiyala
2011-01-18 17:26 ` [PATCH 2/4] omap: hsmmc: Rename and cleanup omap_hsmmc_dma_cleanup Kishore Kadiyala
2011-01-18 17:26 ` [PATCH 3/4] omap4: hsmmc: Adding ADMA support for MMC1 & MMC2 controllers Kishore Kadiyala
2011-01-18 17:26 ` [PATCH 4/4] omap4: hsmmc: enable ADMA for MMC1 & MMC2 Kishore Kadiyala
2011-01-20 17:42 ` Tony Lindgren [this message]
2011-02-03 6:14 ` [PATCH 0/4] omap4: hsmmc: Adding ADMA support Kadiyala, Kishore
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=20110120174226.GX4957@atomide.com \
--to=tony@atomide.com \
--cc=cjb@laptop.org \
--cc=kishore.kadiyala@ti.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