From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] The purpose of enabling CONFIG_PCI_BOOTDELAY
Date: Thu, 25 Mar 2010 05:49:11 +0100 [thread overview]
Message-ID: <201003250549.12030.sr@denx.de> (raw)
In-Reply-To: <c166aa9f1003241434t624ced3cv812dc4561ea4681b@mail.gmail.com>
On Wednesday 24 March 2010 22:34:59 Andrew Dyer wrote:
> >> What is the purpose of CONFIG_PCI_BOOTDELAY? I am using uboot version
> >
> > Adding a delay so the PCI controllers can come up and stabilize.
> >
> >> Specifically in my case, all the resets on my board have occurred well
> >> before (500 msec) this portion of the code would execute, so it would
> >> seem safe to say that any peripherals like PCI controllers would be
> >> satisfied reset-wise.
> >
> > 500ms is not safe. We have seen cases (for example on 440SP / 440SPe)
> > where 5...10 seconds (!) were needed.
>
> I've seen this as well, so I agree that 500ms seems reasonable for a
> general value. Per the PCI 2.3 spec, the time is supposed to be min.
> 100mS.
Per PCI 2.2, the PCI target must respond to config accesses within 2^25 clock
cycles after #RST is de-asserted (PCI System Architecture, fourth edition,
page 321). With 33MHz this is approx. 1 second.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-03-25 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 20:49 [U-Boot] The purpose of enabling CONFIG_PCI_BOOTDELAY Mike.Johnson at apc.com
2010-03-24 21:10 ` Wolfgang Denk
2010-03-24 21:34 ` Andrew Dyer
2010-03-25 4:49 ` Stefan Roese [this message]
2010-03-25 8:26 ` Matthias Fuchs
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=201003250549.12030.sr@denx.de \
--to=sr@denx.de \
--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