On Wed, Jun 11, 2014 at 10:14:40AM +0800, Peter Chen wrote: > Hi Greg, > > Currently, we can't disable auto probe function during booting > if both device and device driver register code are built in due > to .drivers_autoprobe is a private value for bus core and this > value can only be changed by sys entry. Then don't build them into the kernel :) > It causes we can't implement feature that the user can choose > manual binding and auto binding through module parameters. Wait, you just asked about building the stuff into the kernel, not a module. > Eg, the default binding is automatic, but the user can override > it by module parameter. Do we do that for any other "bus" anywhere? > Let's take USB peripheral as an example, there is a device for > udc, and a device driver for usb gadget driver, at default, we want > the device to be bound to driver automatically, this is what > we have done now. But if there are more than one udcs and gadget > drivers (eg one B port for mass storage, another B port for usb ethernet), > the user may want to have specific binding (eg, udc-0 -> mass storage, > udc-1 -> usb ethernet), so the binding will be established > after rootfs has mounted. (This feature is implementing) Then there better be a way to describe this on the kernel command line (i.e. module paramaters), right? Which is a total mess, why not just not bind anything in this case and let the user pick what they want? > From what I read code, we can't implement above feature, but I may > be wrong, if you have some solutions, give me some hints please. > If there is no solution for above feature, do we agree with exporting > .drivers_autoprobe for bus driver or something similar? I don't understand what you mean by this, care to show me with code? thanks, greg k-h -- 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
