linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Slark Xiao" <slark_xiao@163.com>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: "Reinhard Speyerer" <rspmn@arcor.de>,
	johan@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re:Re: Re: Re: [PATCH] [V2,1/1]USB: serial: option: add Foxconn T77W175 composition 0x901d
Date: Tue, 17 Aug 2021 10:27:05 +0800 (CST)	[thread overview]
Message-ID: <ba9a424.f5f.17b51ef0b9d.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <YRpJN414JQyfyEGo@kroah.com>

















At 2021-08-16 19:17:11, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>On Mon, Aug 16, 2021 at 05:25:20PM +0800, Slark Xiao wrote:
>> At 2021-08-16 17:20:59, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>> >On Mon, Aug 16, 2021 at 05:17:00PM +0800, Slark Xiao wrote:
>> >>   So should I use USB_DEVICE_INTERFACE_NUMBER(QUALCOMM_VENDOR_ID, 0x901d, 0x00) to bind Diag port only?
>> >
>> >Why is this device using the QUALCOMM vendor id anyway?  Is this allowed
>> >by Qualcomm?
>> >
>> >thanks,
>> >
>> >greg k-h
>> 
>> Hi Greg,
>>   Our product are designed based on Qualcomm SDX55 platform. So it still support Qualcomm vendor ID.
>>   I think there is no infringement about this ID combo.
>
>Do you have permission from Qualcomm to use their vendor id?  I know
>some vendors get very upset about this...
>
>Why not use your own vendor id?
>
>thanks,
>
>greg k-h

Hi Greg,
   As Qualcomm mainly provide service to their customer, like Samsung, Apple, Huawei, Quectel, Foxconn, Sierra and so on, so I believe all available VID/PIDs are allowed to use. 
   I also checked who is using Qualcomm's VID in the whole kernel, and I found only some old platform (Gobi 1K,2K,3K which don't do any update for almost more than 10 years) in qcserial.c and ZTE, SIMcom, Quectel in option.c are using this VID. Seems Qualcomm won't do this update in the kernel side by themselves(let's say some new PID, 901x,902x,903x,904x,905x...90Fx, and 91xx). 
   About the question why not use our own VID, because this PCIE+USB mode is for debug purpose. We need to keep a common debug settings for both Linux and Windows platform, also for all our customers like Lenovo, Dell, HP, Telit. 
   Hope you can understand that.

Thanks
Slark

  reply	other threads:[~2021-08-17  2:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16  3:54 [PATCH] [V2,1/1]USB: serial: option: add Foxconn T77W175 composition 0x901d Slark Xiao
2021-08-16  9:04 ` Reinhard Speyerer
2021-08-16  9:17   ` Slark Xiao
2021-08-16  9:20     ` Greg KH
2021-08-16  9:25       ` Slark Xiao
2021-08-16 11:17         ` Greg KH
2021-08-17  2:27           ` Slark Xiao [this message]
2021-08-17  6:33             ` Greg KH
2021-08-17  6:51               ` Slark Xiao
2021-08-16 15:47     ` Reinhard Speyerer

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=ba9a424.f5f.17b51ef0b9d.Coremail.slark_xiao@163.com \
    --to=slark_xiao@163.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rspmn@arcor.de \
    /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).