n_gsm.c: use synchronous hangup in GSM TTY to speed up TTY closing

BZ: 14928

This patch is reverting the usage of the WA_VHANGUP_CLOCK work around initiallyaimed at avoiding the usage of a synchronous hangup. The workaround was notonly inserting a 250 ms delay per DLCI close, but also was actually delayingthose hangup after the main TTY close (as those hangup were scheduled on thesame system queue as the calling hangup), which is not the intended sequence.This patch is reverting the use of this workaround as it was wrong.If the non-regression prove this patch worthwhile, then a cleaner patch setshall be put in place to remove the unnecessary code and misleading comments.
Signed-off-by: samix.lebsir <samix.lebsir@intel.com>
Change-Id: I22af64c4c2eb5d993959e6a387bb731d68766106
Reviewed-on: http://android.intel.com:8080/29961
Reviewed-by: Robert, Denis <denis.robert@intel.com>
Tested-by: Robert, Denis <denis.robert@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
index 6bca951..2359c96 100644 (file)
--- a/drivers/tty/n_gsm.c
+++ b/drivers/tty/n_gsm.c
@@ -79,7 +79,7 @@ module_param(debug, int, 0600);
 #define        GSM_NET_TX_TIMEOUT (HZ*10)
 
 /* Workarounds */
-#define  WA_VHANGUP_CLOCK
+#undef  WA_VHANGUP_CLOCK
 
 /**
  *     struct gsm_mux_net      -       network interface