Re: problem with converting from at91_spi to atmel_spi (AT91RM9200)

[Ivan Kuten <ivan.kuten-NihHnkIkDZhBDgjK7y7TUQ@public.gmane.org>]

On 25 May 2007 09:07:24 +0200
Andrew Victor wrote:

> hi,
> 
> > static struct spi_board_info dk_spi_devices[] = {
> >         {       /* DataFlash chip */
> >                 .modalias       = "mtd_dataflash",
> >                 .chip_select    = 0,
> >                 .max_speed_hz   = 15 * 1000 * 1000,
> >         },
> > 
> > are broken cause all of them have chip_select = 0 ?
> 
> I doubt it.
> 
> The DK board definitely works.
> All SAN People's RM9200-based products have DataFlash on CS0 - boot from
> CS0, mount root filesystem (cramfs) on CS0, writable JFFS2 partition on
> CS0.
> 
> That's with legacy SPI and at91_dataflash.c. (ie, CS0 under SPI
> control).
> 

In such a case it should have

static struct spi_board_info dk_spi_devices[] = {
         {       /* DataFlash chip */
//                 .modalias       = "mtd_dataflash",
                 .modalias       = "at91_dataflash",
                 .chip_select    = 0,
                 .max_speed_hz   = 15 * 1000 * 1000,
         },

Cause from my understanding "mtd_dataflash" triggers usage of new SPI framework (driver/spi/atmel_spi.c).

What I currently have:
at91_dataflash.c + 2.6.20+maxim + legacy SPI - working
at91_dataflash.c + 2.6.22rc1+maxim + legacy SPI - not working
mtd_dataflash.c + 2.6.20+maxim + atmel_spi.c - not working
mtd_dataflash.c + 2.6.22rc1+maxim + atmel_spi.c - not working

Now I'm trying understand what was changed between 2.6.20+maxim and 2.6.22rc1+maxim

Best regards, Ivan




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/