[#5687] SPI read/write be wrong after suspend to memory and resume

Document created by Aaronwu Employee on Sep 5, 2013
Version 1Show Document
  • View in full screen mode

[#5687] SPI read/write be wrong after suspend to memory and resume

Submitted By: Barry Song

Open Date

2009-11-16 21:28:21    

Priority:

Medium     Assignee:

Barry Song

Status:

Open     Fixed In Release:

N/A

Found In Release:

2010R1     Release:

Category:

Drivers     Board:

N/A

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

gcc 4.3.4 (svn-3672)

App binary format:

N/A     

Summary: SPI read/write be wrong after suspend to memory and resume

Details:

 

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.

 

Follow-ups

 

--- Barry Song                                               2009-11-16 23:08:15

Assign to me since that causes bug [#5633] and task [#5686] is assigned to me.

Information is:

If using gpio mode chipselect in ad1836/ad1938 in arch, all work normal after

spi suspend/resume.

So it maybe is related with chip select.

 

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes