Dave, regarding your:
 
Well that's really 4-wire SPI, with no chip-select.

I don't know if the OMAP SPI supports the notion of "no-chip-select".

You might just have to specify that there is a chip select and not use
it (which is fine - it's an output pin).

Yes.

The controller omap2_mcspi.c has this comment:

/* standard 4-wire master mode:  SCK, MOSI/out, MISO/in, nCS
     * REVISIT: this controller could support SPI_3WIRE mode.
     */

Regarding your:

After your system has booted up, what does

ls /sys/class/platform/devices
ls /sys/class/platform/drivers

show?

root@overo:~# ls /sys/devices/platform
ehci-omap.0 omap-mcbsp.1 omap2_mcspi.1 omapfb serial8250.2
i2c_omap.1 omap-mcbsp.2 omap2_mcspi.2 power smsc911x.0
i2c_omap.3 omap-mcbsp.3 omap2_mcspi.3 regulatory.0 smsc911x.1
mmci-omap-hs.0 omap-mcbsp.4 omap2_mcspi.4 serial8250 soc-audio
mmci-omap-hs.1 omap-mcbsp.5 omap_wdt serial8250.0 uevent
musb_hdrc omap2-nand omapdss serial8250.1
root@overo:~# ls /sys/
block bus class dev devices firmware fs kernel module power
root@overo:~# ls /sys/class
bdi graphics leds net sound usbmon
block hwmon mdio_bus regulator spi_master vc
bluetooth i2c-adapter mem rtc spidev vtconsole
display i2c-dev misc scsi_device tty
firmware ieee80211 mmc_host scsi_disk ubi
gpio input mtd scsi_host usb_device
root@overo:~# ls /sys/class/display
root@overo:~# ls /sys/class/graphics
fb0 fb1 fb2 fbcon
root@overo:~# ls /sys/class/firmware
timeout
root@overo:~# ls /sys/class/spi_master
spi1 spi2 spi3 spi4
root@overo:~# ls /sys/class/spidev
root@overo:~# ls /sys/class/misc
cpu_dma_latency network_throughput twl4030-madc watchdog
network_latency psaux ubi_ctrl
root@overo:~# ls /sys/
block bus class dev devices firmware fs kernel module power
root@overo:~# ls /sys/devices
omapdss platform system virtual
root@overo:~# ls /sys/devices/virtual
bdi gpio input misc net tty vc
block graphics mem mtd sound usbmon vtconsole
root@overo:~#


 
 

On Thu, Feb 25, 2010 at 11:07 AM, Dave Hylands <dhylands@gmail.com> wrote:
Hi Tony,

On Thu, Feb 25, 2010 at 10:33 AM, Tony Oxendahl <toxend@gmail.com> wrote:
> Quick clarification here, Dave, about your:
>
>> I'm not familiar enough with the omap to know the answer to that. Most
>> of the SPI stuff I've worked with has separate MOSI/MISO lines. The
>> hardware would need special support to support both 3-wire and 4-wire
>> (since in 3-wire the MOSI/MISO share a pin), and I don't know what the
>> OMAP has.
>
> The 3-wire ADC 1278 is MISO, MOSI, Clock.
>
> No Chip Select.
> Like if 1278 bends the SPI protocol.
> The question of how, is asked at TI and pending .
>
> (in 1278 terminology the three wires are DOUT, DIN, SCLK)

Well that's really 4-wire SPI, with no chip-select.

I don't know if the OMAP SPI supports the notion of "no-chip-select".

You might just have to specify that there is a chip select and not use
it (which is fine - it's an output pin).

--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users