Ticket #567: 0001-fsogsmd-fix-suspend-resume-issue-surfaced-after-intr.patch

File 0001-fsogsmd-fix-suspend-resume-issue-surfaced-after-intr.patch, 1.5 KB (added by PaulFertser, 23 months ago)

  • fsogsmd/src/lib/modem.vala 

    From fcb4a52d4e09124eb4442cdaf57575a49c92017a Mon Sep 17 00:00:00 2001
From: Paul Fertser <fercerpav@gmail.com>
Date: Sun, 27 Jun 2010 00:31:03 +0400
Subject: [PATCH] fsogsmd: fix suspend/resume issue surfaced after introduction of OM flow control

Modem's suspend() should wait for the channels' suspend() to complete
before calling lowlevel suspend and changing state. Without that
flowcontrol gets activated too early and the device immediately
resumes. Do the same for resume() for consistency and cleanness.

Signed-off-by: Paul Fertser <fercerpav@gmail.com>
---
 fsogsmd/src/lib/modem.vala |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/fsogsmd/src/lib/modem.vala b/fsogsmd/src/lib/modem.vala
index 33cee8d..34c9a83 100644
    a b public abstract class FsoGsm.AbstractModem : FsoGsm.Modem, FsoFramework.Abstract 
    699699        var channels = this.channels.values; 
    700700        foreach( var channel in channels ) 
    701701        { 
    702             channel.suspend(); 
     702            yield channel.suspend(); 
    703703        } 
    704704 
    705705        lowlevel.suspend(); 
    … … public abstract class FsoGsm.AbstractModem : FsoGsm.Modem, FsoFramework.Abstract 
    719719        var channels = this.channels.values; 
    720720        foreach( var channel in channels ) 
    721721        { 
    722             channel.resume(); 
     722            yield channel.resume(); 
    723723        } 
    724724 
    725725        advanceToState( modem_status_before_suspend, true ); // force