Thanks Carlos,

Finally I managed to get SPI driver working. Original's driver problem was
due to invalid configuration, invalid bit polling (to check end of
transaction) and my error, when I assumed that msleep(1) sleeps for ~1ms.
Indeed it slept for 15-20 ms.

Btw, do you know why there is no SPI driver in MV by default? As I know
there is some complex SPI infrastructure which is not ready yet... Do you
know where can find more information on this (assuming I'd like to share my
driver with the rest of community [but I need to talk to my boss first])?

Regards,
Kirill 

-----Original Message-----
From: Carlos Ojea [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 30, 2006 10:51 AM
To: Kirill Sukhonosenko
Cc: [email protected]
Subject: Re: SPI issue

> I finally tried to setup SPI according to data sheet (SPRUE32) but I think
> data sheet is wrong. It states (see below) that configuration should be
done
> while in reset mode (SPIGCR0: RESET bit). But it doesn't work.

I agree and I also saw that behaviour. I write a 0x00000001 to SPIGCR0
(spi out of reset) and I do all the configuration.
After all the configuration, I put spi into reset and then out of
reset before writing to SPIGCR1to activate it.
I am configuring spi just as you describe, but I am not using
interrupts nor delays.

Regards,
Carlos



_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to