All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bjorn@mork.no>
To: Richard Weinberger <richard@nod.at>
Cc: gregkh@linuxfoundation.org, dcbw@redhat.com, jhovold@gmail.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: Add Option GTM681W to qcserial device table.
Date: Fri, 24 May 2013 20:25:05 +0200	[thread overview]
Message-ID: <87ehcwfd6m.fsf@nemi.mork.no> (raw)
In-Reply-To: <519F88CB.4020500@nod.at> (Richard Weinberger's message of "Fri, 24 May 2013 17:35:39 +0200")

Richard Weinberger <richard@nod.at> writes:
> Am 24.05.2013 15:18, schrieb Bjørn Mork:
>> Richard Weinberger <richard@nod.at> writes:
>>
>>> The Option GTM681W uses a qualcomm chip and can be
>>> served by the qcserial device driver.
>>
>> Should it also be added to the qmi_wwan driver?
>
> Don't know. But I can happily test it. :)
> Can you please explain me how to use the qmi_wwan driver?
> I've never used it.

The QMI management protocol is delegated to userspace using a
/dev/cdc-wdmX character device.  So you need a userspace component to
test the driver, like for example libqmi. See 
http://sigquit.wordpress.com/2012/08/20/an-introduction-to-libqmi/ for a
short intro.

This library is packaged in Debian.  Don't know the status of other
distros. 

The driver supports dynamic device IDs, so if you have qcserial bound to
all serial ports, and there is a QMI interface with no driver bound yet,
then testing should be as easy as

 modprobe qmi_wwan
 echo "0af0 8120" >/sys/bus/usb/drivers/qmi_wwan/new_id
 qmicli -d /dev/cdc-wdm0 --dms-get-manufacturer



Bjørn

  reply	other threads:[~2013-05-24 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 10:01 [PATCH] serial: Add Option GTM681W to qcserial device table Richard Weinberger
2013-05-24 13:18 ` Bjørn Mork
2013-05-24 15:35   ` Richard Weinberger
2013-05-24 18:25     ` Bjørn Mork [this message]
2013-05-24 22:34       ` Dan Williams

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=87ehcwfd6m.fsf@nemi.mork.no \
    --to=bjorn@mork.no \
    --cc=dcbw@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhovold@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.