#9631 NORM 1.5-har: DCON doesn't assert correct status during resume

[Zarro Boogs per Child]

#9631: DCON doesn't assert correct status during resume
--------------------------------+-------------------------------------------
           Reporter:  pgf       |       Owner:  wad           
               Type:  defect    |      Status:  new           
           Priority:  normal    |   Milestone:  1.5-hardware-C
          Component:  hardware  |     Version:  1.5-C2        
         Resolution:            |    Keywords:                
        Next_action:  diagnose  |    Verified:  0             
Deployment_affected:            |   Blockedby:                
           Blocking:            |  
--------------------------------+-------------------------------------------
Changes (by pgf):

 * cc: pgf, rsmith (added)
  * version:  1.5-B2 => 1.5-C2


Comment:

 it turns out that the reason we don't see a proper 01 status acknowledging
 our "dcon unload" operation is that the "dcon unload" operation (i.e, our
 write of DCONLOAD to '1') is redundant.

 we set DCONLOAD to 0 before we suspend.  when we return from suspend, it
 is _already_ set to 1.  (these before/after values confirmed by
 debugging.)  for whatever reason, i think this means the DCON has already
 entered pass-thru mode.  need to wire up a board to verify.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9631#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system