On 02/04/2015 04:16 PM, Peter Chen wrote:
On Wed, Feb 4, 2015 at 4:01 PM, Zhangfei Gao <zhangfei.gao@xxxxxxxxxx> wrote:
Since phy is definitely used usb controller, load the phy
earlier rather than using defer probe to make boot time shorter.
Signed-off-by: Zhangfei Gao <zhangfei.gao@xxxxxxxxxx>
---
drivers/usb/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/Makefile b/drivers/usb/Makefile
index 2f1e2aa..d8926c6 100644
--- a/drivers/usb/Makefile
+++ b/drivers/usb/Makefile
@@ -5,6 +5,7 @@
# Object files in subdirectories
obj-$(CONFIG_USB) += core/
+obj-$(CONFIG_USB_SUPPORT) += phy/
obj-$(CONFIG_USB_DWC3) += dwc3/
obj-$(CONFIG_USB_DWC2) += dwc2/
@@ -48,7 +49,6 @@ obj-$(CONFIG_USB_MICROTEK) += image/
obj-$(CONFIG_USB_SERIAL) += serial/
obj-$(CONFIG_USB) += misc/
-obj-$(CONFIG_USB_SUPPORT) += phy/
obj-$(CONFIG_EARLY_PRINTK_DBGP) += early/
obj-$(CONFIG_USB_ATM) += atm/
--
The similar patch posted before, you may use probe deferral in your controller
driver if the PHY is not ready, besides, both controller and phy
driver may be built
as modules.
Yes, probe deferral is still used in the controller.
For example, dwc2 every time use defer probe to wait phy probe complete.
However since they are in the same folder, and we already know the
sequence, is it better to change the sequence to make it quicker.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
