After gadget bus introducing, the bind/unbind udc to configfs driver will use standard device-model's usage, which are the entries of bind and unbind at device driver. Signed-off-by: Peter Chen <peter.chen@xxxxxxxxxxxxx> --- Documentation/usb/gadget_configfs.txt | 13 ++++++------- 1 files changed, 6 insertions(+), 7 deletions(-) diff --git a/Documentation/usb/gadget_configfs.txt b/Documentation/usb/gadget_configfs.txt index 4cf53e4..fd4119c 100644 --- a/Documentation/usb/gadget_configfs.txt +++ b/Documentation/usb/gadget_configfs.txt @@ -53,6 +53,7 @@ http://www.spinics.net/lists/linux-usb/msg76388.html) $ modprobe libcomposite $ mount none $CONFIGFS_HOME -t configfs +$ echo 0 > /sys/bus/usb_gadget/drivers_autoprobe where CONFIGFS_HOME is the mount point for configfs @@ -189,7 +190,6 @@ An example directory structure might look like this: ./functions/ncm.usb0/qmult ./functions/ncm.usb0/host_addr ./functions/ncm.usb0/dev_addr -./UDC ./bcdUSB ./bcdDevice ./idProduct @@ -203,18 +203,17 @@ An example directory structure might look like this: Such a gadget must be finally enabled so that the USB host can enumerate it. In order to enable the gadget it must be bound to a UDC (USB Device Controller). -$ echo <udc name> > UDC +$ echo <udc name> > /sys/bus/usb_gadget/drivers/<configfs driver>/bind -where <udc name> is one of those found in /sys/class/udc/* +where <udc name> is one of those found in /sys/bus/usb_gadget/devices/* +where <configfs driver> is one of those found in /sys/bus/usb_gadget/drivers/* e.g.: - -$ echo s3c-hsotg > UDC - +$ echo udc-0 > /sys/bus/usb_gadget/drivers/configfs-gadget.0/bind 6. Disabling the gadget ----------------------- -$ echo "" > UDC +$ echo udc-0 > /sys/bus/usb_gadget/drivers/configfs-gadget.0/unbind 7. Cleaning up -------------- -- 1.7.8 -- 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
