public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Imre Deak <imre.deak@nokia.com>
Cc: omap-linux <linux-omap-open-source@linux.omap.com>
Subject: Re: Edge selecton on SPI bus
Date: Mon, 15 May 2006 11:59:36 -0700	[thread overview]
Message-ID: <200605151159.37793.david-b@pacbell.net> (raw)
In-Reply-To: <1147691115.32613.10.camel@mammoth.research.nokia.com>

On Monday 15 May 2006 4:05 am, Imre Deak wrote:
> Hi,
> 
> I think the edge selection in the omap_uwire and omap2_mcspi is borked.
> I have a patch for it, but I'd like to ask first if my assumption is
> right:
> On the SPI / uWire bus by definition you can only configure a mode (one
> of the 4 modes), in which the read / write takes place on opposite
> edges. That is you can't configure for example a read rising edge /
> write rising edge mode.

That's my understanding, yes.  Consider that if you connect MOSI directly
to MISO for a loopback configuration, what you send is supposed to exactly
match what you receive ... that couldn't happen if there were no settling
time between setting MOSI and reading MISO.

That WRITE_FALLING | READ_FALLING always did look goofy, but I recall it
as more or less a direct translation from the old driver.  In any case
the REVISIT note seems to have gotten lost.

- Dave



> On OMAP2 this I even see from the fact that you can set the reading edge
> and the writing edge is implied.
> 
> --Imre
> 
> 

  reply	other threads:[~2006-05-15 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 11:05 Edge selecton on SPI bus Imre Deak
2006-05-15 18:59 ` David Brownell [this message]
2006-05-16 22:12   ` [PATCH 0/3] ARM: OMAP: SPI edge selection [was Re: Edge selecton on SPI bus] Imre Deak
2006-05-17  2:50     ` David Brownell
2006-05-17 10:13       ` Imre Deak
2006-05-26 23:43       ` Tony Lindgren

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=200605151159.37793.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=imre.deak@nokia.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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