From: Wolfgang Wegner Date: Thu, 6 May 2010 17:59:30 +0200 Subject: [U-Boot] OT: SD/MMC-over-SPI and speed in linux In-Reply-To: <201005061613.41462.alexander.stein@systec-electronic.com> References: <20100506131314.GE23839@leila.ping.de> <201005061533.54056.alexander.stein@systec-electronic.com> <20100506135944.GG23839@leila.ping.de> <201005061613.41462.alexander.stein@systec-electronic.com> Message-ID: <20100506155930.GH23839@leila.ping.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On Thu, May 06, 2010 at 04:13:41PM +0200, Alexander Stein wrote: > > I can't say much about actual transfer rates. But i noticed a real slowdown > when the filesystem buffer is about to be flushed. > We are using a COldfire 5484 and AFAIK there is no DMA for SPI, at least we > don't use it. I used M54451EVB/M54455EVB as a starting point, both use eDMA for SPI by default. Sorry, don't know about MCF547x/548x. Things are clearing up now: as far as I could see, there are no real timing-relevant things changed in mmc_spi code, BUT the underlying SPI driver is crucial. Setting the same default timing values found in mcf5445x-devices.c in U-Boot (CONFIG_SYS_DSPI_CTAR0), I can degrade the performance of MMC-SPI in U-Boot by a factor of 3, approximately. However, setting the fast default values from U-Boot in the linux kernel (mcf5445x-devices.c) makes things even worse there, too. After all, I am sure now it is only the SPI part I have to investigate further, most probably concerning latency between transfers. Thanks for the comments and sorry for the noise! Best regards, Wolfgang