From: liulongfang <liulongfang@huawei.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: <gregkh@linuxfoundation.org>, <mathias.nyman@intel.com>,
<linux-usb@vger.kernel.org>, <yisen.zhuang@huawei.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] USB:XHCI:Modify XHCI driver for USB2.0 controller
Date: Sat, 27 Feb 2021 11:48:12 +0800 [thread overview]
Message-ID: <7e880f79-8568-7b14-cb2f-4be647538ba1@huawei.com> (raw)
In-Reply-To: <acfdf816-e295-df1d-4039-784fb0d417c4@huawei.com>
On 2021/2/27 11:38, liulongfang wrote:
> On 2021/2/27 0:30, Alan Stern wrote:
>> On Fri, Feb 26, 2021 at 04:21:37PM +0800, Longfang Liu wrote:
>>> Our current XHCI hardware controller has been customized to only
>>> support USB 2.0 ports. When using the current xhci driver, an xhci
>>> controller device and an ehci controller device will be created
>>> automatically.
>>
>> That sentence makes no sense at all. An EHCI controller device is a
>> piece of hardware. How can an xHCI driver, which is a piece of
>> software, create a piece of hardware?
>>
>> Alan Stern
>> .
>>
> The hardware device is a complete USB3.0 controller,
On the hardware, only the hardware connection of the USB2.0 port has been opened
> but I hope to support a USB2.0-only mode through software configuration.
> Thanks.
> Longfang Liu
> .
>
Thanks.
Longfang Liu
next prev parent reply other threads:[~2021-02-27 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 8:21 Longfang Liu
2021-02-26 8:38 ` Greg KH
2021-02-27 3:31 ` liulongfang
2021-03-04 1:35 ` Peter Chen
2021-03-04 4:08 ` liulongfang
2021-02-26 9:22 ` Mathias Nyman
2021-02-27 3:34 ` liulongfang
2021-02-26 16:30 ` Alan Stern
2021-02-27 3:38 ` liulongfang
2021-02-27 3:48 ` liulongfang [this message]
2021-02-27 16:27 ` Alan Stern
2021-03-01 1:58 ` liulongfang
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=7e880f79-8568-7b14-cb2f-4be647538ba1@huawei.com \
--to=liulongfang@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
--cc=yisen.zhuang@huawei.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
all inboxes | Powered by JetHome®