On Tuesday 05 May 2009, Narnakaje, Snehaprabha wrote: > Initial patch set was sent back in March - > http://linux.omap.com/pipermail/davinci-linux-open-source/2009-March/012210.html > > > This was tested on DM355, but the same driver should > work on DM6446, but requires some device to be connected to SPI.
Which can be done through one of the expansion connectors. I think I saw some protyping boards available, which make it easier to access those signals. > There were some review comments to be addressed on this > patch set, Still not addressed ... though that wiki status page says "target end-of-week 5/1". I hope it didn't slip too far. ;) > but the main discussion was about the EEPROM > driver - should we have a MTD based EEPROM driver or > just the raw EEPROM driver (already part of misc drivers) > was enough to test SPI. And I think the conclusion was to use the standard EEPROM driver, like everyone else is doing. (For a part with only a couple pages of memory, MTD wouldn't be very usable anyway.) Another aspect of this is that writing a new driver that's only ever tested with a DaVinci SPI driver, and preventing use of the standard and well tested EEPROM driver, gives no assurance that the spi_master interface has been properly implemented. Bugs in one could easily cover up bugs in the other. Having it work with the standard EEPROM driver is a weak sort of conformance test, but it's better than nothing. - Dave _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
