Lines Matching +full:in +full:- +full:functions

12 that kernel level composite functions provide when they are added to
15 This in particular means that the composite initialisation functions
16 may not be in init section (ie. may not use the __init tag).
25 them as needed also handling situation when numbers differ in
28 For more information about FunctionFS descriptors see :doc:`functionfs-desc`
40 What I also want to mention is that the FunctionFS is designed in such
41 a way that it is possible to mount it several times so in the end
42 a gadget could use several FunctionFS functions. The idea is that
50   $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
51   $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
52   $ ( cd /dev/ffs-mtp && mtp-daemon ) &
53   $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid
54   $ ( cd /dev/ffs-hid && hid-daemon ) &
56 On kernel level the gadget checks ffs_data->dev_name to identify
59 If no "functions" module parameters is supplied, the driver accepts
62 When "functions" module parameter is supplied, only functions
63 with listed names are accepted. In particular, if the "functions"
64 parameter's value is just a one-element list, then the behaviour
65 is similar to when there is no "functions" at all; however,
69 filesystems have been mounted and USB descriptors of all functions
83 objects between several interfaces, allowing it to transfer data in a
84 zero-copy fashion, for instance between IIO and the USB stack.
103     the size in bytes to transfer (which should generally correspond to