public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: omap_hsmmc: add adma support
Date: Mon, 12 May 2014 10:50:02 -0400	[thread overview]
Message-ID: <20140512145002.GD22182@bill-the-cat> (raw)
In-Reply-To: <5370CFD4.5050309@ti.com>

On Mon, May 12, 2014 at 07:12:44PM +0530, Balaji T K wrote:
> On Monday 12 May 2014 06:58 PM, Tom Rini wrote:
> >On Fri, May 02, 2014 at 07:25:20PM +0530, Balaji T K wrote:
> >
> >>MMC instance 1 and 2 is capable of ADMA in omap4, omap5.
> >>Add support for ADMA and enable ADMA for read/write to
> >>improve mmc throughput.
> >[snip]
> >>@@ -44,12 +45,30 @@
> >>  #undef OMAP_HSMMC_USE_GPIO
> >>  #endif
> >>
> >>+#ifdef CONFIG_SPL_BUILD
> >>+#undef CONFIG_OMAP_MMC_ADMA
> >>+#endif
> >
> >Why?  Especially since a number of the folks interested in this for
> >performance want it for SPL OS mode.  Thanks!
> 
> Because in SoCs like OMAP4/5 mmc1/2 adma doesn't have access to sram.
> So can't have descriptor or src / destination buffers (allocated on stack)
> given by mmc core on sram.

And we can't malloc them?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140512/cebe71ce/attachment.pgp>

  reply	other threads:[~2014-05-12 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 13:55 [U-Boot] [PATCH] mmc: omap_hsmmc: add adma support Balaji T K
2014-05-12 13:21 ` Balaji T K
2014-05-12 13:28 ` Tom Rini
2014-05-12 13:42   ` Balaji T K
2014-05-12 14:50     ` Tom Rini [this message]
2014-05-15 14:15       ` Balaji T K
2014-05-15 17:55         ` Tom Rini

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=20140512145002.GD22182@bill-the-cat \
    --to=trini@ti.com \
    --cc=u-boot@lists.denx.de \
    /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