1 ==================== 1 ====================
2 How FunctionFS works 2 How FunctionFS works
3 ==================== 3 ====================
4 4
5 Overview 5 Overview
6 ======== 6 ========
7 7
8 From kernel point of view it is just a composi 8 From kernel point of view it is just a composite function with some
9 unique behaviour. It may be added to an USB c 9 unique behaviour. It may be added to an USB configuration only after
10 the user space driver has registered by writin 10 the user space driver has registered by writing descriptors and
11 strings (the user space program has to provide 11 strings (the user space program has to provide the same information
12 that kernel level composite functions provide 12 that kernel level composite functions provide when they are added to
13 the configuration). 13 the configuration).
14 14
15 This in particular means that the composite in 15 This in particular means that the composite initialisation functions
16 may not be in init section (ie. may not use th 16 may not be in init section (ie. may not use the __init tag).
17 17
18 From user space point of view it is a file sys 18 From user space point of view it is a file system which when
19 mounted provides an "ep0" file. User space dr 19 mounted provides an "ep0" file. User space driver need to
20 write descriptors and strings to that file. I 20 write descriptors and strings to that file. It does not need
21 to worry about endpoints, interfaces or string 21 to worry about endpoints, interfaces or strings numbers but
22 simply provide descriptors such as if the func 22 simply provide descriptors such as if the function was the
23 only one (endpoints and strings numbers starti 23 only one (endpoints and strings numbers starting from one and
24 interface numbers starting from zero). The Fu 24 interface numbers starting from zero). The FunctionFS changes
25 them as needed also handling situation when nu 25 them as needed also handling situation when numbers differ in
26 different configurations. 26 different configurations.
27 27
28 For more information about FunctionFS descript <<
29 <<
30 When descriptors and strings are written "ep#" 28 When descriptors and strings are written "ep#" files appear
31 (one for each declared endpoint) which handle 29 (one for each declared endpoint) which handle communication on
32 a single endpoint. Again, FunctionFS takes ca 30 a single endpoint. Again, FunctionFS takes care of the real
33 numbers and changing of the configuration (whi 31 numbers and changing of the configuration (which means that
34 "ep1" file may be really mapped to (say) endpo 32 "ep1" file may be really mapped to (say) endpoint 3 (and when
35 configuration changes to (say) endpoint 2)). 33 configuration changes to (say) endpoint 2)). "ep0" is used
36 for receiving events and handling setup reques 34 for receiving events and handling setup requests.
37 35
38 When all files are closed the function disable 36 When all files are closed the function disables itself.
39 37
40 What I also want to mention is that the Functi 38 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 39 a way that it is possible to mount it several times so in the end
42 a gadget could use several FunctionFS function 40 a gadget could use several FunctionFS functions. The idea is that
43 each FunctionFS instance is identified by the 41 each FunctionFS instance is identified by the device name used
44 when mounting. 42 when mounting.
45 43
46 One can imagine a gadget that has an Ethernet, 44 One can imagine a gadget that has an Ethernet, MTP and HID interfaces
47 where the last two are implemented via Functio 45 where the last two are implemented via FunctionFS. On user space
48 level it would look like this:: 46 level it would look like this::
49 47
50 $ insmod g_ffs.ko idVendor=<ID> iSerialNumbe 48 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
51 $ mkdir /dev/ffs-mtp && mount -t functionfs 49 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
52 $ ( cd /dev/ffs-mtp && mtp-daemon ) & 50 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
53 $ mkdir /dev/ffs-hid && mount -t functionfs 51 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid
54 $ ( cd /dev/ffs-hid && hid-daemon ) & 52 $ ( cd /dev/ffs-hid && hid-daemon ) &
55 53
56 On kernel level the gadget checks ffs_data->de 54 On kernel level the gadget checks ffs_data->dev_name to identify
57 whether its FunctionFS is designed for MTP ("m 55 whether its FunctionFS is designed for MTP ("mtp") or HID ("hid").
58 56
59 If no "functions" module parameters is supplie 57 If no "functions" module parameters is supplied, the driver accepts
60 just one function with any name. 58 just one function with any name.
61 59
62 When "functions" module parameter is supplied, 60 When "functions" module parameter is supplied, only functions
63 with listed names are accepted. In particular, 61 with listed names are accepted. In particular, if the "functions"
64 parameter's value is just a one-element list, 62 parameter's value is just a one-element list, then the behaviour
65 is similar to when there is no "functions" at 63 is similar to when there is no "functions" at all; however,
66 only a function with the specified name is acc 64 only a function with the specified name is accepted.
67 65
68 The gadget is registered only after all the de 66 The gadget is registered only after all the declared function
69 filesystems have been mounted and USB descript 67 filesystems have been mounted and USB descriptors of all functions
70 have been written to their ep0's. 68 have been written to their ep0's.
71 69
72 Conversely, the gadget is unregistered after t 70 Conversely, the gadget is unregistered after the first USB function
73 closes its endpoints. 71 closes its endpoints.
74 72
75 DMABUF interface 73 DMABUF interface
76 ================ 74 ================
77 75
78 FunctionFS additionally supports a DMABUF base 76 FunctionFS additionally supports a DMABUF based interface, where the
79 userspace can attach DMABUF objects (externall 77 userspace can attach DMABUF objects (externally created) to an endpoint,
80 and subsequently use them for data transfers. 78 and subsequently use them for data transfers.
81 79
82 A userspace application can then use this inte 80 A userspace application can then use this interface to share DMABUF
83 objects between several interfaces, allowing i 81 objects between several interfaces, allowing it to transfer data in a
84 zero-copy fashion, for instance between IIO an 82 zero-copy fashion, for instance between IIO and the USB stack.
85 83
86 As part of this interface, three new IOCTLs ha 84 As part of this interface, three new IOCTLs have been added. These three
87 IOCTLs have to be performed on a data endpoint 85 IOCTLs have to be performed on a data endpoint (ie. not ep0). They are:
88 86
89 ``FUNCTIONFS_DMABUF_ATTACH(int)`` 87 ``FUNCTIONFS_DMABUF_ATTACH(int)``
90 Attach the DMABUF object, identified by it 88 Attach the DMABUF object, identified by its file descriptor, to the
91 data endpoint. Returns zero on success, an 89 data endpoint. Returns zero on success, and a negative errno value
92 on error. 90 on error.
93 91
94 ``FUNCTIONFS_DMABUF_DETACH(int)`` 92 ``FUNCTIONFS_DMABUF_DETACH(int)``
95 Detach the given DMABUF object, identified 93 Detach the given DMABUF object, identified by its file descriptor,
96 from the data endpoint. Returns zero on su 94 from the data endpoint. Returns zero on success, and a negative
97 errno value on error. Note that closing th 95 errno value on error. Note that closing the endpoint's file
98 descriptor will automatically detach all a 96 descriptor will automatically detach all attached DMABUFs.
99 97
100 ``FUNCTIONFS_DMABUF_TRANSFER(struct usb_ffs_ 98 ``FUNCTIONFS_DMABUF_TRANSFER(struct usb_ffs_dmabuf_transfer_req *)``
101 Enqueue the previously attached DMABUF to 99 Enqueue the previously attached DMABUF to the transfer queue.
102 The argument is a structure that packs the 100 The argument is a structure that packs the DMABUF's file descriptor,
103 the size in bytes to transfer (which shoul 101 the size in bytes to transfer (which should generally correspond to
104 the size of the DMABUF), and a 'flags' fie 102 the size of the DMABUF), and a 'flags' field which is unused
105 for now. Returns zero on success, and a ne 103 for now. Returns zero on success, and a negative errno value on
106 error. 104 error.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.