summaryrefslogtreecommitdiff
path: root/kernel/rtmutex-debug.c
diff options
context:
space:
mode:
authorBenoit Goby <benoit@android.com>2011-12-12 13:01:23 -0800
committerArve Hjønnevåg <arve@android.com>2013-07-01 13:40:38 -0700
commit5049bbc5d5ff18a011ac4cb00a79e4de17cc1f30 (patch)
treee29f10f575caae45a7421350334a9799d3f24dab /kernel/rtmutex-debug.c
parentdbfb82e58a91c426a14cbcb50a0c663aaf7127fa (diff)
downloadolio-linux-3.10-5049bbc5d5ff18a011ac4cb00a79e4de17cc1f30.tar.xz
olio-linux-3.10-5049bbc5d5ff18a011ac4cb00a79e4de17cc1f30.zip
usb: gadget: Add Android Composite Gadget driver
The Android Gadget driver is a composite driver that allows userspace to change at runtime the list of functions enabled in its configuration and to configure these functions. It supports multiple functions: acm, adb, rndis, mtp/ptp, mass storage and accessory. It is usually controlled by a daemon that changes the configuration based on user settings. For example, rndis is enabled when the user enables sharing the phone data connection and adb (Android Debug Bridge) is only enabled when the user wants to debug applications for security reasons. As an example on how to use it, the following shell commands will make the gadget disconnect from the host and make it be re-enumerated as a composite with 1 rndis and 2 acm interfaces, and a different product id: echo 0 > /sys/class/android_usb/android0/enable echo rndis,acm > /sys/class/android_usb/android0/functions echo 2 > /sys/class/android_usb/android0/f_acm/instances echo 2d01 > /sys/class/android_usb/android0/idProduct echo 1 > /sys/class/android_usb/android0/enable The driver requires a gadget controller that supports software control of the D+ pullup and the controller driver must support disabling the pullup during composite_bind. Signed-off-by: Mike Lockwood <lockwood@android.com> Signed-off-by: Benoit Goby <benoit@android.com>
Diffstat (limited to 'kernel/rtmutex-debug.c')
0 files changed, 0 insertions, 0 deletions