linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Lars Melin <larsm17@gmail.com>,
	Giuseppe Lippolis <giu.lippolis@gmail.com>,
	linux-usb@vger.kernel.org
Subject: usb:serial:optrion: fix dwm-158 3g modem interface
Date: Tue, 24 Apr 2018 19:28:38 +0200	[thread overview]
Message-ID: <20180424172838.GE4615@localhost> (raw)

On Mon, Apr 23, 2018 at 11:54:32AM -0500, Dan Williams wrote:
> On Mon, 2018-04-23 at 14:14 +0700, Lars Melin wrote:

> > Blacklisting interface 4 and 5 is correct because:
> > 
> > MI_00 D-Link Mobile Broadband Device  (cdc_ether)
> > MI_02 D-Link HSPA+DataCard Diagnostics Interface (also ppp modem)
> > MI_03 D-Link HSPA+DataCard NMEA Device
> > MI_04 D-Link HSPA+DataCard Speech Port
> 
> Any idea what format this port speaks?  Some Huawei Qualcomm-based
> devices still use a TTY driver but send/receive 16-bit 8000hz PCM audio
> frames via a serial port.

Wow. Shouldn't this really be handled by an ALSA driver?

Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-04-24 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 17:28 Johan Hovold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-24 17:30 usb:serial:optrion: fix dwm-158 3g modem interface Johan Hovold
2018-04-24  4:21 Dan Williams
2018-04-24  2:55 Lars Melin
2018-04-23 16:54 Dan Williams
2018-04-23  9:02 Johan Hovold
2018-04-23  8:58 Sergei Shtylyov
2018-04-23  8:42 Johan Hovold
2018-04-23  7:14 Lars Melin
2018-04-23  7:03 Giuseppe Lippolis
2018-04-23  7:00 Giuseppe Lippolis

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=20180424172838.GE4615@localhost \
    --to=johan@kernel.org \
    --cc=dcbw@redhat.com \
    --cc=giu.lippolis@gmail.com \
    --cc=larsm17@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    /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).