public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Philip Balister <philip@balister.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: McSPI3 on the BeagleBoard
Date: Tue, 17 Feb 2009 19:18:44 -0800	[thread overview]
Message-ID: <200902171918.45146.david-b@pacbell.net> (raw)
In-Reply-To: <499B4B64.30109@balister.org>

On Tuesday 17 February 2009, Philip Balister wrote:
> 
> A number of people have tried using the McSPI3 interface with the spidev 
> driver. Running the spidev_test program shows data coming out of the 
> interface, but when we connect the SIMO to SOMI pins, the spidev_test 
> program shows only 0's. Someone tried wiring SOMI to +volts and still 
> only saw 0 read.

I took a quick glance, and the pinmuxing looks sort of OK if
you ignore the names ... use the right balls, not XXX:

+       AE2_3430_MCSPI3_CLK,
+       AG5_3430_MCSPI3_SIMO,
+       AH5_3430_MCSPI3_SOMI,
+       AF4_3430_MCSPI3_CS0,
+       AG4_3430_MCSPI3_CS1,

I suggest you start with a more focussed patch, only setting
up McSPI3.  For one thing, the MMC2 pinmuxing will interfere
with this set of MCSPI3 configurations.

Also, start with a less aggressive bit rate than 48 MHz; that
may be OK on a well designed board, but breadboards tend to
show flakiness at much over 10 MHz.

- Dave

  parent reply	other threads:[~2009-02-18  3:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 23:42 McSPI3 on the BeagleBoard Philip Balister
2009-02-18  0:09 ` Tony Lindgren
2009-02-18  3:18 ` David Brownell [this message]
2009-02-19  0:39   ` Philip Balister
2009-02-19  0:53     ` Tony Lindgren
2009-02-19  8:22     ` Gregoire Gentil
2009-02-19 14:14       ` Philip Balister
2009-02-20  8:33         ` Gregoire Gentil
2009-02-20 11:44           ` Grazvydas Ignotas
2009-02-20 19:19           ` Philip Balister

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=200902171918.45146.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=philip@balister.org \
    /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