All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] convention for SPI dummy data?
Date: Fri, 23 Apr 2010 17:49:10 +0200	[thread overview]
Message-ID: <20100423154910.GQ20047@leila.ping.de> (raw)
In-Reply-To: <201004231134.54565.vapier@gentoo.org>

On Fri, Apr 23, 2010 at 11:34:53AM -0400, Mike Frysinger wrote:
[...]
> > the problem exists in the (coldfire) SPI driver, not in the MMC/SD code.
> 
> sorry, i thought you were proposing to fix it in the SPI/MMC driver

no, as far as I can see it is always set to 0xFF there if set explicitly,
i.e. except for the read-only transfers.

> what i've seen so far is that the idle val doesnt matter to most spi devices.  
> so on the Blackfin side, we've been defaulting to 0xff so that things do work 
> "out of the box" for everyone (at least so far).

Sounds good - however I had just sent a patch implementing CONFIG_SPI_IDLE_VAL.

(I am quite hesitating to simply change such a basic default value because
I fear there might be other devices around relying on current behaviour.
On the other hand, my implementation adds 7 lines of preprocessor stuff,
which also does not look really good.)

Regards,
Wolfgang

  reply	other threads:[~2010-04-23 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  8:43 [U-Boot] convention for SPI dummy data? Wolfgang Wegner
2010-04-23 15:08 ` Mike Frysinger
2010-04-23 15:18   ` Wolfgang Wegner
2010-04-23 15:34     ` Wolfgang Wegner
2010-04-23 15:34     ` Mike Frysinger
2010-04-23 15:49       ` Wolfgang Wegner [this message]
2010-04-23 15:43   ` [U-Boot] [PATCH RFC] add CONFIG_SPI_IDLE_VAL for cf_spi.c to allow use of spi_mmc Wolfgang Wegner
2011-06-13 18:27     ` Terje B. Nilsen

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=20100423154910.GQ20047@leila.ping.de \
    --to=wolfgang@leila.ping.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.