[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210226163004.GB1392547@rowland.harvard.edu>
Date: Fri, 26 Feb 2021 11:30:04 -0500
From: Alan Stern <stern@...land.harvard.edu>
To: Longfang Liu <liulongfang@...wei.com>
Cc: gregkh@...uxfoundation.org, mathias.nyman@...el.com,
linux-usb@...r.kernel.org, yisen.zhuang@...wei.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] USB:XHCI:Modify XHCI driver for USB2.0 controller
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
Powered by blists - more mailing lists