public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: at91sam9n12: change EBI IO to high drive mode
Date: Wed, 17 Jul 2013 15:05:09 +0200	[thread overview]
Message-ID: <20130717150509.76521769@lilith> (raw)
In-Reply-To: <0296489B-402C-4076-9CCC-C5E99D91EEF6@prograde.net>

Hi Michael,

On Wed, 17 Jul 2013 07:27:36 -0400, Michael Cashwell
<mboards@prograde.net> wrote:

> On Jul 17, 2013, at 6:42 AM, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
> 
> > I understand the symptom. What I don't undestand is how come NAND
> > does not keep its data lines in high impedance when its chip select is
> > inactive, which it is when DDR is being accessed.
> 
> Chip selects prevent contention but they do not make the load vanish.
> A deselected chip is not electrically the same as a non-populated chip,
> especially at high frequencies.
> 
> Think of it another way. CMOS pins that are input-only are always high-z
> but they still must be counted as a load when adding up the fan out seen
> by the upstream output driver.

They must be counted as load alright, I understand this. But that
leaves / leads to some questions:

- how come the issue never appeared so far? If this is so basic a
  problem, I would have expected it to show up as soon as the SoC gets
  frequent use.

- doesn't the driving lines' fan-out take this load into account?
  Again, I would expect a device's drive to be strong enough to
  overcome a few Hi-Zs, since that's an expected type of load.

- why is the issue not symmetric? Techno's CMOS or CMOS-like, I guess,
  so there is no reason to pull up rather than down. Unless there are
  pulldowns in the NAND or elsewhere, but then it's not Hi-Z any more.

> -Mike

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-07-17 13:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17  9:14 [U-Boot] [PATCH] arm: at91sam9n12: change EBI IO to high drive mode Bo Shen
2013-07-17 10:10 ` Albert ARIBAUD
2013-07-17 10:27   ` Bo Shen
2013-07-17 10:42     ` Albert ARIBAUD
2013-07-17 11:27       ` Michael Cashwell
2013-07-17 13:05         ` Albert ARIBAUD [this message]
2013-07-17 17:05           ` Michael Cashwell
2013-07-19  1:51       ` Bo Shen
2013-07-19  6:54         ` Albert ARIBAUD
2013-07-19 12:13 ` Tom Rini
2013-07-20 23:02   ` Andreas Bießmann
2013-07-22  1:59     ` Bo Shen
2013-07-22 14:11 ` [U-Boot] " 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=20130717150509.76521769@lilith \
    --to=albert.u.boot@aribaud.net \
    --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