All of lore.kernel.org
 help / color / mirror / Atom feed
From: "谭 永林" <yonglin.tan@outlook.com>
To: Johan Hovold <johan@kernel.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 回复: 回复: [PATCH] USB: serial: option: add Quectel EM060K modem
Date: Mon, 8 Aug 2022 06:38:25 +0000	[thread overview]
Message-ID: <MEYP282MB237442B77909EB1FEC56AA2BFD639@MEYP282MB2374.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Yuovy5ukT9V1ydKS@hovoldconsulting.com>

Dear Johan,

The QDSS port only be used for capturing modem's log. The user application acquires the modem's log by accessing the BULK_IN EP. And no other operation requirements on this interface. 

Best Regards.

-----邮件原件-----
发件人: Johan Hovold <johan@kernel.org> 
发送时间: 2022年8月3日 16:20
收件人: 谭 永林 <yonglin.tan@outlook.com>
抄送: gregkh@linuxfoundation.org; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org
主题: Re: 回复: [PATCH] USB: serial: option: add Quectel EM060K modem

On Sat, Jul 30, 2022 at 07:32:47AM +0000, 谭 永林 wrote:

> The last interface is used for Qualcomm WWAN module's QDSS(Qualcomm 
> Debug Sub-System) port. Users use the QDSS interface to acquire Modem 
> subsystem log. It is used to work with DIAG port. Therefore, we don't 
> have to bind this interface with any driver.

Thanks for the details (I can add QDSS to the summary of the interface layout in the commit message when applying).

But are you saying that it's not needed because that data is available also over the DIAG port? Or is there some libusb driver that should be used to access the QDSS port?

Johan

  reply	other threads:[~2022-08-08  6:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 11:28 [PATCH] USB: serial: option: add Quectel EM060K modem Yonglin Tan
2022-07-24  8:41 ` Johan Hovold
2022-07-30  7:32   ` 回复: " 谭 永林
2022-08-03  8:20     ` Johan Hovold
2022-08-08  6:38       ` 谭 永林 [this message]
2022-08-29 13:17 ` Johan Hovold

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=MEYP282MB237442B77909EB1FEC56AA2BFD639@MEYP282MB2374.AUSP282.PROD.OUTLOOK.COM \
    --to=yonglin.tan@outlook.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.