> I found out a couple more things about this. > > If I do "rmmod dwc3" first, and then do "rmmod dwc3-pci", it doesn't > crash. > dwc3-pci will release dwc3 and its resources at its removal. So, dwc3 core must be released first, then glue layer. Since there are no relationship between core and glue layer, If user unload module in incorrect order, the oops may occur, the phy driver is the same situation. For such kinds of case, do we need to fix at kernel layer? or using user space method to fix? > On a related note, if I just do "modprobe dwc3-pci", then dwc3.ko > doesn't get loaded. I have to do "modprobe dwc3" too, to get > everything loaded. Shouldn't dwc3.ko be a dependency of dwc3-pci.ko, > and get loaded automatically? Could this missing dependency also > explain the crash on "rmmod dwc3-pci"? > -- BR, Peter Chen -- 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
