Hi, BJ Opp spiffera, Thursday 23 October 2008: > The only chatter I've seen on this mailing list seems to > lean toward people pushing others to use /dev/mtd to talk spi but that > really doesn't make any sense unless they mean to use that when trying > to talk to a nand or other such block device.
Well, AFAIK in MV kernel there isn't a userspace general interface. That's because you may want to implement a device driver in kernel space. Implementing a kernel driver is quite simple, though: you only have to configure your spi port, filing the struct davinci_spi_config_t of your platform data, and after that use function like spi_write(), spi_write_then_read(), spi_read(), and so on... You saw talks on /dev/mtd, because the tipical example of spi device driver is mtd/devices/at25xxA_eeprom.c Take it as reference for SPI functions, and simply discard the mtd part, if you don't need it. -- Andrea Gasparini ---- ImaVis S.r.l. ---- web: www.imavis.com _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
