From: Arnav Das <arnavdas29@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
spi-devel-general@lists.sourceforge.net
Subject: General SPI question
Date: Fri, 24 Apr 2009 11:58:08 +0530 [thread overview]
Message-ID: <8ee9e87c0904232328j7f912eb6v3d0b9cb0321793a9@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
Hi,
Thanks a lot and sorry for the mistakes. I have gone through the trm of the
adc as well as the omap driver. my question is that i want to interact the
adc to the board. now should i directly use the omap driver or should i mak
one of my own. if i make one of my own then i would like to know how would
the spi registers be changed by driver. should it include the omap2 driver
or is the fuctionality provided directly when i include spi.h.
another doubt: when and why is the spidev.c/h used?
i am deeply grateful towards you for helping me out
thanks
Arnav
On Fri, Apr 24, 2009 at 11:50 AM, David Brownell <david-b@pacbell.net>wrote:
> 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
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1983 bytes --]
reply other threads:[~2009-04-24 6:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8ee9e87c0904232328j7f912eb6v3d0b9cb0321793a9@mail.gmail.com \
--to=arnavdas29@gmail.com \
--cc=david-b@pacbell.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=sr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox