Searched refs:creating (Results 1 – 25 of 207) sorted by relevance
123456789
40 The function name to use when creating the function directory is "acm".79 The function name to use when creating the function directory is "ecm".92 and after creating the functions/ecm.<instance name> they contain default119 The function name to use when creating the function directory is "geth".132 and after creating the functions/ecm.<instance name> they contain default159 The function name to use when creating the function directory is "eem".172 and after creating the functions/eem.<instance name> they contain default199 The function name to use when creating the function directory is "ffs".202 After creating the directory there is a new instance (a "device") of FunctionFS223 The function name to use when creating the function directory is "hid".[all …]
21 will result in creating a hrtimer trigger in the IIO subsystem.34 in creating a dummy IIO device in the IIO subystem.
7 is defined or calculated by the layer that is creating the
51 Userspace applications interested in creating mediated54 creating mediated device of this type.
11 One very interesting use of dm-zero is for creating "sparse" devices in20 To create a sparse device, start by creating a dm-zero device that's the
23 For creating and maintaining the FAQ.26 For creating the FAQ, and the leafsite HOWTO.
48 shared resources without creating a new process. unshare() is a natural56 where creating a new process to control sharing/unsharing of process58 when creating a new process using fork or clone, unshare() can benefit83 client requests by creating processes that share resources such as85 decide what needs to be shared at the time of creating the process139 shared by explicit request to share them when creating a process143 shared execution context without creating a new process.
6 different i2c slave address,presently for which we are statically creating i2c
14 This script downloads and extracts the firmware, creating wd719x-risc.bin and
38 - creating traffic class 10:1::
24 in the hardware driver for creating the MSI interrupts.
10 * Do not add anything that would result in dtc creating node "/__fixups__".
21 creating HP-UX logical volumes easy from HP-UX disk block device file
24 blocks are shared between different functions, creating dependencies
21 The intention of creating this framework is to bring the PHY drivers spread94 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in163 This subsystem is pm runtime enabled. So while creating the PHY,
6 may have when creating tasks living in different namespaces.
6 creating a video pipeline.
19 used for creating new files. Default values: '????'.
11 10 bit mode. This is used for creating device names in sysfs. It is also
17 This torture test consists of creating a number of kernel threads which21 creating more kthreads.
16 GICv3 implementations with hardware compatibility support allow creating a17 guest GICv2 through this interface. For information on creating a guest GICv3
22 to the driver creating them because it might want to drive them, meaning78 loops over the passed in ndev creating devices and registering them.
16 initialisation code by creating a struct regulator_consumer_supply for
25 descriptor. The former is moved into the container by creating a character
31 DMA_ATTR_NO_KERNEL_MAPPING lets the platform to avoid creating a kernel32 virtual mapping for the allocated buffer. On some architectures creating