public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MTD/SPI/FLASH: add support for Ramtron FRAMs using SPI
Date: Thu, 26 Aug 2010 02:12:20 -0400	[thread overview]
Message-ID: <201008260212.20777.vapier@gentoo.org> (raw)
In-Reply-To: <4C760243.6030102@emk-elektronik.de>

On Thursday, August 26, 2010 01:57:23 Reinhard Meyer wrote:
> Dear Mike Frysinger,
> > #if defined(CONFIG_SPI_FRAM_RAMTRON)
> > # define IDCODE_LEN 10
> > #else
> > # define IDCODE_LEN 5
> > #endif
> 
> OK, see below. Can't we have it 10 generally? The impact should be
> negligible?

hrm, i guess ... but i didnt even really like raising it to the 5 for one 
specific family ...

> > for the second, what do you get back when you issue the idcode ?  0xff ? 
> > we already have a fall back case for this with stmicro, so perhaps we
> > should
> >
> > generalize this further too.  after the vendor id switch statement, we do:
> 
> If MISO has no pull-up the result is indeterminate, the chip simply lets
> MISO float when it does not honor the read-id command.
> 
> I'll add a comment to that file that a pull-up is required for non-standard
> devices to be detected. Otherwise, depending on random noise, a false
> detection of a standard device is not entirely impossible.

that sounds reasonable to me
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100826/10488897/attachment.pgp 

  reply	other threads:[~2010-08-26  6:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 12:47 [U-Boot] [PATCH] MTD/SPI/FLASH: add support for Ramtron FRAMs using SPI Reinhard Meyer
2010-08-26  2:31 ` Mike Frysinger
2010-08-26  5:57   ` Reinhard Meyer
2010-08-26  6:12     ` Mike Frysinger [this message]
2010-08-26  6:24       ` Reinhard Meyer
2010-08-26  8:27       ` Reinhard Meyer
2010-08-26  9:11         ` Mike Frysinger
2010-08-26 20:00           ` Reinhard Meyer
2010-08-28 21:48             ` Mike Frysinger
2010-08-28 22:15               ` Reinhard Meyer
2010-08-28 22:26                 ` Mike Frysinger
2010-08-28 23:17               ` Mike Frysinger
2010-08-28 23:45                 ` Reinhard Meyer
2010-08-29  0:14                   ` Mike Frysinger
2010-08-29  1:59                     ` Reinhard Meyer
2010-08-29  2:26                       ` Mike Frysinger
2010-08-29  3:35                         ` Reinhard Meyer
2010-08-29  4:34                           ` Mike Frysinger
2010-08-29  4:52                             ` Reinhard Meyer
2010-09-07 20:12                             ` Peter Tyser
2010-09-07 19:38     ` Wolfgang Denk

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=201008260212.20777.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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