From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756285AbcBVWyE (ORCPT ); Mon, 22 Feb 2016 17:54:04 -0500 Received: from [46.54.226.45] ([46.54.226.45]:48848 "EHLO mail.tnode.com" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1756192AbcBVWx6 (ORCPT ); Mon, 22 Feb 2016 17:53:58 -0500 From: Andrej Krpic To: xinhuix.pan@intel.com Cc: linux-kernel@vger.kernel.org, jslaby@suse.com, gregkh@linuxfoundation.org, Andrej Krpic Subject: [PATCH 0/8] tty: n_gsm: Make mux work as a responder station Date: Mon, 22 Feb 2016 23:53:08 +0100 Message-Id: <1456181596-11736-1-git-send-email-ak77@tnode.com> X-Mailer: git-send-email 2.7.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When using n_gsm you have to explicitly set it to work as a initiator station. This led me to believe that it can also work as a responder. In a use case where I needed responder station mux I came to the conclusion that it actually does not work. Second and third patch fix dealings with frame C/R bit that then enable mux to work as a responder station. Next patches in the series then fix bugs that were found after two instances of n_gsm connected over null-modem cable were used. First patch fixes formatting errors, such as space before comma, and most of the warnings reported by the checkpatch script. Andrej Krpic (8): tty: n_gsm: fix formatting errors tty: n_gsm: fix C/R bit when sending as a responder tty: n_gsm: make mux work as a responder station tty: n_gsm: send DM response when accessing an invalid channel tty: n_gsm: replace dead code with a meaningful comment tty: n_gsm: add missing length field in control channel commands tty: n_gsm: properly format Modem Status Command message tty: n_gsm: Enable reception of frames separated with a single SOF marker drivers/tty/n_gsm.c | 191 +++++++++++++++++++++++++++++++++------------------- 1 file changed, 123 insertions(+), 68 deletions(-) -- 2.7.0