| /linux/Documentation/usb/ |
| H A D | gadget-testing.rst | 41 The function name to use when creating the function directory is "acm".
80 The function name to use when creating the function directory is "ecm".
93 and after creating the functions/ecm.<instance name> they contain default
120 The function name to use when creating the function directory is "geth".
133 and after creating the functions/ecm.<instance name> they contain default
160 The function name to use when creating the function directory is "eem".
173 and after creating the functions/eem.<instance name> they contain default
200 The function name to use when creating the function directory is "ffs".
203 After creating the directory there is a new instance (a "device") of FunctionFS
232 The function name to use when creating the function directory is "hid".
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-iio | 21 will result in creating a hrtimer trigger in the IIO subsystem.
34 in creating a dummy IIO device in the IIO subsystem.
|
| H A D | sysfs-class-fpga-region | 7 is defined or calculated by the layer that is creating the
|
| H A D | sysfs-bus-vfio-mdev | 51 Userspace applications interested in creating mediated
54 creating mediated device of this type.
|
| /linux/Documentation/userspace-api/ |
| H A D | lsm.rst | 31 creating file system objects.
36 creating key objects.
47 creating socket objects.
|
| H A D | unshare.rst | 48 shared resources without creating a new process. unshare() is a natural
56 where creating a new process to control sharing/unsharing of process
58 when creating a new process using fork or clone, unshare() can benefit
83 client requests by creating processes that share resources such as
85 decide what needs to be shared at the time of creating the process
139 shared by explicit request to share them when creating a process
143 shared execution context without creating a new process.
|
| /linux/Documentation/networking/device_drivers/wwan/ |
| H A D | iosm.rst | 70 traffic. Iproute network utility is used for creating "wwan0-X" network
74 The userspace management application is responsible for creating new IP link
77 For example, creating new IP link for a MBIM IP session with SessionId 1:
|
| H A D | t7xx.rst | 129 traffic. Iproute network utility is used for creating "wwan0-X" network
132 The userspace management application is responsible for creating new IP link
135 For example, creating new IP link for a MBIM IP session with SessionId 1:
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | zero.rst | 11 One very interesting use of dm-zero is for creating "sparse" devices in
20 To create a sparse device, start by creating a dm-zero device that's the
|
| /linux/Documentation/isdn/ |
| H A D | credits.rst | 23 For creating and maintaining the FAQ.
26 For creating the FAQ, and the leafsite HOWTO.
|
| /linux/fs/afs/ |
| H A D | server.c | 183 bool creating = false; in afs_lookup_server() local
218 creating = true; in afs_lookup_server()
228 if (creating) { in afs_lookup_server()
276 creating = true; in afs_lookup_server()
|
| /linux/drivers/bus/fsl-mc/ |
| H A D | Kconfig | 22 Provides userspace support for interrogating, creating, destroying or
|
| /linux/Documentation/scsi/ |
| H A D | wd719x.rst | 14 This script downloads and extracts the firmware, creating wd719x-risc.bin and
|
| /linux/Documentation/sound/ |
| H A D | utimers.rst | 61 So, the example code for creating and triggering the timer would be:
93 More detailed example of creating and ticking the timer could be found
|
| /linux/drivers/of/unittest-data/ |
| H A D | overlay_common.dtsi | 8 * Do not add anything that would result in dtc creating node "/__fixups__".
|
| /linux/drivers/peci/ |
| H A D | Kconfig | 24 responsible for creating auxiliary devices that can subsequently
|
| /linux/drivers/platform/wmi/ |
| H A D | Kconfig | 31 scheme when creating WMI devices. Doing so might be necessary for some
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | net_cls.rst | 38 - creating traffic class 10:1::
|
| /linux/drivers/ntb/ |
| H A D | Kconfig | 24 in the hardware driver for creating the MSI interrupts.
|
| /linux/Documentation/doc-guide/ |
| H A D | parse-headers.rst | 44 and enum ``symbol``, creating cross-references for all of them.
160 At the same struct, instead of creating one cross reference per symbol,
|
| /linux/Documentation/driver-api/phy/ |
| H A D | phy.rst | 21 The intention of creating this framework is to bring the PHY drivers spread
94 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in
190 This subsystem is pm runtime enabled. So while creating the PHY,
|
| /linux/fs/freevxfs/ |
| H A D | Kconfig | 22 creating HP-UX logical volumes easy from HP-UX disk block device file
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-intro.rst | 24 blocks are shared between different functions, creating dependencies
|
| /linux/Documentation/admin-guide/namespaces/ |
| H A D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
|
| /linux/tools/testing/selftests/net/rds/ |
| H A D | README.txt | 4 These scripts provide a coverage test for RDS-TCP by creating two
|