From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 12 May 2014 10:50:02 -0400 Subject: [U-Boot] [PATCH] mmc: omap_hsmmc: add adma support In-Reply-To: <5370CFD4.5050309@ti.com> References: <1399038920-19023-1-git-send-email-balajitk@ti.com> <20140512132853.GZ22182@bill-the-cat> <5370CFD4.5050309@ti.com> Message-ID: <20140512145002.GD22182@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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: