From: David Brownell <david-b@pacbell.net>
To: linux-omap-open-source@linux.omap.com
Subject: Re: SPI pins on omap5912
Date: Wed, 24 Jan 2007 11:25:24 -0800 [thread overview]
Message-ID: <200701241125.24668.david-b@pacbell.net> (raw)
In-Reply-To: <BAY130-F68DE0B2ECF2ECFB623DA6F8AC0@phx.gbl>
On Wednesday 24 January 2007 6:21 am, zil iram wrote:
> Hi,
>
> I am using linux 2.6.17 on the omap5912 board. I would like to use the spif
> pins, spif_cs0, spif_din, spif_dout, spif_sck on the board and connect them
> to the spi pins on my device. Do I still need to make my own controller
> driver for the spi framework?
yes
> Or can I use the omap_uwire?
not unless you're using the microwire controller ...
next prev parent reply other threads:[~2007-01-24 19:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 5:42 Re :RE: Accessing DSP MMU on OMAP SDP2430 rajeev s
2007-01-24 14:21 ` SPI pins on omap5912 zil iram
2007-01-24 19:25 ` David Brownell [this message]
2007-01-25 2:06 ` SPI controller " zil iram
2007-01-25 2:33 ` David Brownell
2007-01-25 5:41 ` 3430/Linux MMC Driver Support Alawala, Jayaprakash
2007-01-25 5:47 ` Syed Mohammed, Khasim
2007-01-26 10:32 ` SPI controller on omap5912 zil iram
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=200701241125.24668.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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