On Wednesday 07 February 2007 8:15 am, Haavard Skinnemoen wrote: > Driver for the Atmel on-chip SPI master controller. > > Tested primarily on AVR32/AT32AP7000/ATSTK1000 using mtd_dataflash and > the jffs2 filesystem.
Call me paranoid, but until such controller drivers can withstand loads placed by filesystems I have a hard time trusting them! ;) Various drivers using smaller transfers (control for LCD or audio DAC, sensors, EEPROM access) have also been reported to work. > Should also work fine on various AT91 ARM-based > chips like AT91SAM926x. And answering a question we had: I did get confirmation from one person, saying that they'd used a previous version of this driver on at91rm9200 with success. I think that answers Andrew Victor's basic question about whether the "legacy" at91 SPI driver is ready to go away ... the main unresolved issue being a replacement for that old userspace interface. (And that issue is nearly resolved too.) > Hardware documentation can be found in the AT32AP7000 data sheet, > which can be downloaded from > > http://www.atmel.com/dyn/products/datasheets.asp?family_id=682 > > Signed-off-by: Haavard Skinnemoen <[EMAIL PROTECTED]> Signed-off-by: David Brownell <[EMAIL PROTECTED]> > --- > Note that this driver depends on the arch-neutral GPIO API patches > currently in -mm. So this should follow the merge of the AVR32 architecture updates, and the AT91 GPIO patch, to prevent creation of configs that won't build. ISTR that AT91 also needs some arch updates to make it _run_ properly (to use the same board init conventions), but IMO this can merge before those if that simplifies the process. (That is, no need to wait for AT91 patches to go from Andrew to Russell to Linus first.) Thanks for making this driver happen! - Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
