public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell•net>
To: Arnav Das <arnavdas29@gmail•com>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>,
	spi-devel-general@lists•sourceforge.net
Subject: Re: general SPI question (WAS: [PATCH v6] spi: Add PPC4xx SPI driver)
Date: Thu, 23 Apr 2009 23:20:30 -0700	[thread overview]
Message-ID: <200904232320.30609.david-b@pacbell.net> (raw)
In-Reply-To: <8ee9e87c0904232032sc7ef5e7ibf058618fca8c1a0@mail.gmail.com>

On Thursday 23 April 2009, Arnav Das wrote:
> i am a newbie

Lesson #1:  make sure your Subject: lines match the message
topic (I did a partial repair) and don't post to the wrong
list (e.g. PPC lists for OMAP questions).


> and am doing a project on beagle board(running 
> omap3530). i am interfacing an adc(ads7886) to the beagleboard via
> spi. need to know how the spi works

Read the ads7886 data sheet, in this case.  It uses
a subset of SPI ... no input commands, just a 12-bit
sample returned each time chipselect pulses.


> and how a module can access the 
> spi registers of the omap. if someones already made an adc driver can
> they mail me?

Use drivers/spi/omap2_mcspi.c on OMAP3 boards, at
least to start with.  If you want streaming conversions
you may want to use different modes than are currently
supported by that driver.

- Dave

      reply	other threads:[~2009-04-24  6:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 10:40 [PATCH v6] spi: Add PPC4xx SPI driver Stefan Roese
2009-04-22  5:36 ` David Brownell
2009-04-22  8:29   ` Stefan Roese
2009-04-22  8:56     ` David Brownell
2009-04-22 20:00 ` David Brownell
2009-04-24  3:32   ` [spi-devel-general] " Arnav Das
2009-04-24  6:20     ` David Brownell [this message]

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=200904232320.30609.david-b@pacbell.net \
    --to=david-b@pacbell$(echo .)net \
    --cc=arnavdas29@gmail$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=spi-devel-general@lists$(echo .)sourceforge.net \
    --cc=sr@denx$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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