[#5687] SPI read/write be wrong after suspend to memory and resume
Submitted By: Barry Song
Open Fixed In Release:
Found In Release:
BF537 Silicon Revision:
Is this bug repeatable?:
Uboot version or rev.:
Toolchain version or rev.:
gcc 4.3.4 (svn-3672)
App binary format:
Summary: SPI read/write be wrong after suspend to memory and resume
After suspending to memory(rtcwake -s 10 -m mem) and resuming, SPI read/write will be wrong.
Without insmoding any audio drivers, but insmod spi-bf5xx, run rtcwake -s 10 -m mem. After resume, insmod ad1938 or ad1836, write any value to any registers by SPI, read value is 0.
Without insmoding any audio drivers, and don't insmod spi-bf5xx, run rtcwake -s 10 -m mem. After resume, insmod spi-bf5xx, insmod ad1938 or ad1836, write any value to any registers by SPI, read value is right.
So it is sure spi driver can't resume to work normally after suspending to mem.
That makes audio using spi drivers can't work normally after suspending too.
--- Barry Song 2009-11-16 23:08:15
Assign to me since that causes bug [#5633] and task [#5686] is assigned to me.
If using gpio mode chipselect in ad1836/ad1938 in arch, all work normal after
So it maybe is related with chip select.
File Name File Type File Size Posted By
No Files Were Found