Openmoko Bug #2180: stable-tracking: 'rxserr' UART messages

[Openmoko Public Trac]

#2180: stable-tracking: 'rxserr' UART messages
-----------------------------+----------------------------------------------
 Reporter:  laforge          |          Owner:  openmoko-kernel         
     Type:  defect           |         Status:  new                     
 Priority:  high             |      Milestone:  FSO                     
Component:  System Software  |        Version:                          
 Severity:  major            |       Keywords:  gps s3x24xx_serial rxerr
 Haspatch:  0                |      Blockedby:                          
Estimated:                   |    Patchreview:                          
 Blocking:                   |   Reproducible:                          
-----------------------------+----------------------------------------------

Comment(by andy):

 100ms would still be death at 9600.

 Wow I see what this one is anyway, when we do a multi read or write
 sequence, we have to send a STOP command when we've had enough.  I had it
 perform the send action of the STOP command inside the glamo-mci interrupt
 service :-[  Thanks a lot for the great call trace.

 This has to be split out into a workqueue, I will sort it out today
 hopefully.

 There was a generic MCI CONFIG option I noticed and enabled in 2.6.28
 period that more aggressively chains up sequential read and write actions
 into one longer bulk read or write on the bus... this can have increased
 probability of STOP issue because single page reads don't need STOP
 action.

 But, Harald won't have this issue since he doesn't have Glamo.  I don't
 think it's Calypso in his other platform either.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2180#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac