On Sun, Apr 19, 2015 at 11:46:12AM +0800, Zhuang Jin Can wrote: > Some usb3 devices may not support usb3 lpm well. > The patch adds a sysfs to enable/disable u1 or u2 of the port.The > settings apply to both before and after device enumeration. > Supported values are "0" - u1 and u2 are disabled, "u1" - only u1 is > enabled, "u2" - only u2 is enabled, "u1_u2" - u1 and u2 are enabled. > > The interface is useful for testing some USB3 devices during > development, and provides a way to disable usb3 lpm if the issues can > not be fixed in final products. How is a user supposed to "know" to make this setting for a device? Why can't the kernel automatically set this value properly? Why does it need to be a kernel issue at all? And when you are doing development of broken devices, the kernel doesn't have to support you, you can run with debugging patches of your own until you fix your firmware :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
