Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 4 Mar 2021 09:35:49 +0800
From:   Peter Chen <peter.chen@kernel.org>
To:     liulongfang <liulongfang@huawei.com>
Cc:     Greg KH <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
Message-ID: <20210304013548.GA16596@nchen>
References: <1614327697-1021-1-git-send-email-liulongfang@huawei.com>
 <YDizmDmu6Kh264Pv@kroah.com>
 <87cc8b54-f530-cce0-3ea2-f879436ff5f7@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87cc8b54-f530-cce0-3ea2-f879436ff5f7@huawei.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 21-02-27 11:31:00, liulongfang wrote:
> On 2021/2/26 16:38, Greg KH 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.
> > 
> > That sounds like a spec violation, right?  Why do you want to do this?
> > 
> > greg k-h
> > .
> > 
> I hope to support a USB2.0-only mode on the XHCI controller
> through software configuration.
> Thanks.

If your hardware has disabled USB3 logic, when the USB3 device is plugged,
since there are no RX signal on the bus, the device will not enable USB3
logic, and only USB2 signals will be on the bus, there are only USB devices on
USB2 roothub later. So, any issues you have met?

-- 

Thanks,
Peter Chen