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] Falcon mode boot support
Date: Wed, 17 Dec 2014 16:02:26 -0500	[thread overview]
Message-ID: <20141217210226.GP20704@bill-the-cat> (raw)
In-Reply-To: <5491af14.42fac20a.10ed.3bd4SMTPIN_ADDED_BROKEN@mx.google.com>

On Wed, Dec 17, 2014 at 04:27:37PM -0000, Andy Pont wrote:
> Hi Tom,
> 
> Following the experiment that yielded the following results:
> 
> > U-Boot> time sf read ${loadaddr} 0x200000 ${loadsize}
> > 
> > I get the following back:
> > 
> > SF: 2541352 bytes @ 0x200000 Read: OK
> > time: 2.447 seconds
> 
> I have done some reading and poking around and have added the
> OMAP3_MCSPI_CHCONF_TURBO flag to the SPI channel enablement in the
> omap3_spi_read() function within omap3_spi.c and now the same command takes
> 1.279 seconds to execute.
> 
> I have also added a couple of printf() statements around the call to read
> the flash device that loads the kernel image in spi_load_image_os() and the
> timestamps on the output to the serial console consistently show that it is
> taking around 3.5 seconds to load the same kernel image.
> 
> I haven't fully looked into what is going on as I haven't yet found the full
> call path from spi_flash_read() in spi_flash.h to when it eventually results
> in the call to omap3_spi_read() and so it may be doing more and I'm not
> actually comparing apples with apples.
> 
> Could you (or maybe Jagannadha as SPI custodian) point me in the right
> direction?

I suspect that this might be related to the general problem on these
part families where SPL isn't as fast as we expect it to be, perhaps
cache related.

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

  parent reply	other threads:[~2014-12-17 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <548f0a77.c768c20a.2e45.26a0SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-15 17:23 ` [U-Boot] Falcon mode boot support Tom Rini
2014-12-15 21:08   ` Andy Pont
     [not found]   ` <548f4dd3.0677c20a.5db4.14a9SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-15 22:08     ` Tom Rini
2014-12-16 12:58       ` Andy Pont
     [not found]       ` <54902c90.e44bc20a.557b.5c5bSMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-16 14:30         ` Tom Rini
2014-12-16 14:48           ` Andy Pont
2014-12-17 16:27             ` Andy Pont
     [not found]             ` <5491af14.42fac20a.10ed.3bd4SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-17 21:02               ` Tom Rini [this message]
2014-12-18 12:28                 ` Andy Pont
2014-12-15 16:20 Andy Pont

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=20141217210226.GP20704@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