From: Aleksander Morgado <aleksander@aleksander.es>
To: oliver@neukum.org, davem@davemloft.net
Cc: stefano.godeas@u-blox.com, marco.demarco@u-blox.com,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
Aleksander Morgado <aleksander@aleksander.es>
Subject: [PATCH v2] cdc_ncm: flag the u-blox TOBY-L4 as wwan
Date: Fri, 25 Aug 2017 15:39:16 +0200 [thread overview]
Message-ID: <20170825133916.13948-1-aleksander@aleksander.es> (raw)
In-Reply-To: <20170825125946.12812-1-aleksander@aleksander.es>
The u-blox TOBY-L4 is a LTE Advanced (Cat 6) module with HSPA+ and 2G
fallback.
Unlike the TOBY-L2, this module has one single USB layout and exposes
several TTYs for control and a NCM interface for data. Connecting this
module may be done just by activating the desired PDP context with
'AT+CGACT=1,<cid>' and then running DHCP on the NCM interface.
Signed-off-by: Aleksander Morgado <aleksander@aleksander.es>
---
drivers/net/usb/cdc_ncm.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/net/usb/cdc_ncm.c
index 811b18215cae..47cab1bde065 100644
--- a/drivers/net/usb/cdc_ncm.c
+++ b/drivers/net/usb/cdc_ncm.c
@@ -1758,6 +1758,13 @@ static const struct usb_device_id cdc_devs[] = {
.driver_info = (unsigned long)&wwan_noarp_info,
},
+ /* u-blox TOBY-L4 */
+ { USB_DEVICE_AND_INTERFACE_INFO(0x1546, 0x1010,
+ USB_CLASS_COMM,
+ USB_CDC_SUBCLASS_NCM, USB_CDC_PROTO_NONE),
+ .driver_info = (unsigned long)&wwan_info,
+ },
+
/* Generic CDC-NCM devices */
{ USB_INTERFACE_INFO(USB_CLASS_COMM,
USB_CDC_SUBCLASS_NCM, USB_CDC_PROTO_NONE),
--
2.14.1
next prev parent reply other threads:[~2017-08-25 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 12:59 [PATCH] cdc_ncm: flag the ublox TOBY-L4 as wwan Aleksander Morgado
2017-08-25 13:22 ` Greg KH
2017-08-25 13:30 ` Aleksander Morgado
2017-08-25 13:39 ` Aleksander Morgado [this message]
2017-08-28 18:25 ` [PATCH v2] cdc_ncm: flag the u-blox " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170825133916.13948-1-aleksander@aleksander.es \
--to=aleksander@aleksander.es \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marco.demarco@u-blox.com \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stefano.godeas@u-blox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).