All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregoire Gentil <gregoire@gentil.com>
To: Philip Balister <philip@balister.org>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: McSPI3 on the BeagleBoard
Date: Thu, 19 Feb 2009 00:22:27 -0800	[thread overview]
Message-ID: <1235031747.13828.1.camel@localhost> (raw)
In-Reply-To: <499CAA27.5020500@balister.org>

Philip,

Can you please post here or on the Beagleboard mailing list the u-boot
patch? This muxpin is very tricky and I have experienced many problems
when set up in the kernel while it seems to work better from u-boot -
don't know why,

Grégoire


On Wed, 2009-02-18 at 19:39 -0500, Philip Balister wrote:
> David Brownell wrote:
> > 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.
> 
> OK, more results:
> 
> 1) I do not intend for this to go into the kernel, well unless there is 
> an outcry from beagle users :)
> 
> 
> Steve Sakoman suggested I do the pinmux setup in u-boot and furnished me 
> with a small u-boot patch. Using this patch and removing the pinmux 
> stuff from the kernel patch lead to working spidev_test.
> 
> The 48 MHz is the max rate, spidev_test defaults to 500 kHz. (but it 
> appears to work at 48 MHz also.
> 
> Thanks for taking a look at this!
> 
> Philip
> 
> PS: I love photos: http://www.flickr.com/photos/32615155@N00/3291304854/

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-02-19  8:22 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
2009-02-19  0:39   ` Philip Balister
2009-02-19  0:53     ` Tony Lindgren
2009-02-19  8:22     ` Gregoire Gentil [this message]
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=1235031747.13828.1.camel@localhost \
    --to=gregoire@gentil.com \
    --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 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.