summaryrefslogtreecommitdiff
path: root/arch/score
diff options
context:
space:
mode:
authorLars Poeschel <poeschel@lemonage.de>2014-01-07 12:34:37 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-02-22 21:32:26 (GMT)
commitebcca55846e8c4fda540dcf62b58e2f726e798b8 (patch)
treeb5f27065d5f5c267e4c852c390d57c3a6b091ab9 /arch/score
parent44ff717ceeadf2035504f9eee48f0f14333cae2c (diff)
downloadlinux-fsl-qoriq-ebcca55846e8c4fda540dcf62b58e2f726e798b8.tar.xz
tty: n_gsm: Fix for modems with brk in modem status control
commit 3ac06b905655b3ef2fd2196bab36e4587e1e4e4f upstream. 3GPP TS 07.10 states in section 5.4.6.3.7: "The length byte contains the value 2 or 3 ... depending on the break signal." The break byte is optional and if it is sent, the length is 3. In fact the driver was not able to work with modems that send this break byte in their modem status control message. If the modem just sends the break byte if it is really set, then weird things might happen. The code for deconding the modem status to the internal linux presentation in gsm_process_modem has already a big comment about this 2 or 3 byte length thing and it is already able to decode the brk, but the code calling the gsm_process_modem function in gsm_control_modem does not encode it and hand it over the right way. This patch fixes this. Without this fix if the modem sends the brk byte in it's modem status control message the driver will hang when opening a muxed channel. Signed-off-by: Lars Poeschel <poeschel@lemonage.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/score')
0 files changed, 0 insertions, 0 deletions