On Tue, Feb 14, 2017 at 10:41:06AM -0500, Alan Stern wrote: > On Tue, 14 Feb 2017, Greg Kroah-Hartman wrote: > > > On Tue, Feb 14, 2017 at 08:46:16PM +0800, yuan linyu wrote: > > > From: yuan linyu <linyu.y...@alcatel-sbell.com.cn> > > > > > > one usage is in embedded system usb host controller is non-PCI based, > > > chooe N in such system will not compile PCI code/function of USB. > > > > I'm really sorry, but I can not parse this very well. What exact > > problem does this patch solve? Why is it needed? It seems to just keep > > the same functionality that we currently have today, right? > > > > We already distinguish PCI/non-PCI based USB host controllers by using > > the CONFIG_PCI option, why do we need to add another one? > > The problem that this patch tries to fix arises when you have a system > where CONFIG_PCI is enabled for other reasons, but the USB hardware is > non-PCI. In that situation, you don't want to build the PCI-based USB > drivers unnecessarily.
Ok, that would be a good start of a description of this config option :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
