Searched full:created (Results 1 – 25 of 611) sorted by relevance
12345678910>>...25
| /Documentation/ABI/testing/ |
| D | sysfs-bus-vfio-mdev | 9 Each supported type is a directory whose name is created
41 devices sysfs entries which are created of this <type-id>.
48 devices of type <type-id> that can be created. This is a
53 the number of available instances could be created before
69 mediated device that will get created of type <type-id>.
81 mediated device that will get created of type <type-id>.
102 directory of which this mediated device is created.
|
| D | sysfs-class-vduse | 15 This directory entry is created for the control device
23 This directory entry is created when a VDUSE device is
24 created via the control device.
|
| D | sysfs-bus-event_source-devices-hv_gpci | 92 * This sysfs file will be created only for power10 and above platforms.
96 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
124 * This sysfs file will be created only for power10 and above platforms.
128 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
156 * This sysfs file will be created only for power10 and above platforms.
160 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
188 * This sysfs file will be created only for power10 and above platforms.
192 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
220 * This sysfs file will be created only for power10 and above platforms.
224 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
|
| D | configfs-rdma_cm | 12 for this HCA has to be created:
28 will be created with this TOS as default.
|
| D | sysfs-class-rtrs-server | 6 directory entry with the name of that session is created in here.
12 Description: When new path is created by writing to "add_path" entry on client side,
13 a directory entry named as <source address>@<destination address> is created
|
| D | ppc-memtrace | 17 debugfs files will be created. Once memory is successfully
18 removed from each node, the following files are created. To
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 63 A symlink is created in the bus's 'devices' directory that points to
66 A symlink is created in the driver's 'devices' directory that points
69 A directory for the device is created in the class's directory. A
70 symlink is created in that directory that points to the device's
73 A symlink can be created (though this isn't done yet) in the device's
75 top-level directory. One can also be created to point to its driver's
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 39 entries corresponding to EPF driver will be created by the EPF core.
56 (These entries are created by the framework when any new <EPF Device> is
57 created)
86 be created by the user to represent the virtual functions that are bound to
95 entries corresponding to EPC device will be created by the EPC core.
109 <EPF Device>. These symbolic links should be created by the user to
116 all the EPF devices are created and linked with the EPC device.
|
| /Documentation/leds/ |
| D | uleds.rst | 12 When the driver is loaded, a character device is created at /dev/uleds. To
22 A new LED class device will be created with the name given. The name can be
34 Multiple LED class devices are created by opening additional file handles to
|
| /Documentation/userspace-api/media/dvb/ |
| D | net-add-if.rst | 36 ULE) and the interface number for the new interface to be created. When
38 created.
41 filled with the number of the created interface.
|
| D | net-get-if.rst | 13 NET_GET_IF - Read the configuration data of an interface created via - :ref:`NET_ADD_IF <net>`.
38 created yet with :ref:`NET_ADD_IF <net>`, it will return -1 and fill
|
| /Documentation/filesystems/ |
| D | efivarfs.rst | 7 The efivarfs filesystem was created to address the shortcomings of
14 Variables can be created, deleted and modified with the efivarfs
23 files that are not well-known standardized variables are created
|
| D | configfs.rst | 21 With sysfs, an object is created in kernel (for example, when a device
25 write(2). The important point is that the object is created and
29 A configfs config_item is created via an explicit userspace operation:
54 An item is created via mkdir(2). The item's attributes will also
98 A fakenbd connection can be created with mkdir(2). The name is
127 Items are created and destroyed inside a config_group. A group is a
129 Items are created by mkdir(2) and removed by rmdir(2), but configfs
166 Whether statically defined in a source file or created by a parent
263 A config_item cannot live in a vacuum. The only way one can be created
356 The group is where child config_items are created. For a subsystem,
[all …]
|
| D | debugfs.rst | 39 created in the debugfs root. On success, the return value is a struct
58 the return value will be a dentry pointer to the created file,
76 created with any of::
154 any code which does so in the mainline. Note that all files created with
198 of its elements. Note: Once array is created its size can not be changed.
226 Symbolic links can be created with debugfs_create_symlink().
229 there is no automatic cleanup of any directories created in debugfs. If a
242 pointer for every debugfs file they created so that all files could be
|
| D | hpfs.rst | 71 well. If you create 'a. ...', the file 'a' will be created, but you can still
84 attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only
86 options are created. Once created, the extended attributes are never deleted,
93 special 4-byte extended attribute "DEV" will be created containing the device
118 file has a pointer to codepage its name is in. However OS/2 was created in
121 Once I booted English OS/2 working in cp 850 and I created a file on my 852
126 really what IBM developers wanted? But problems continued. When I created in
193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
198 probably because of directories created with old version of this driver.
201 whole created by this driver, it is BUG - let me know about it.
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 36 as well as the major and minor numbers of the character device that was created.
38 example ``/dev/tpm10`` was created, the number (``dev_num``) 10 is returned.
40 Once the device has been created, the driver will immediately try to talk
|
| /Documentation/usb/ |
| D | gadget_configfs.rst | 62 For each gadget to be created its corresponding directory must be created::
82 In order to have a place to store them, a strings subdirectory must be created
93 Further custom string descriptors can be created as directories within the
107 directories must be created:
120 Each configuration also needs its strings, so a subdirectory must be created
137 directory must be created::
158 At this moment a number of gadgets is created, each of which has a number of
364 a number of its default sub-groups created automatically.
|
| /Documentation/devicetree/bindings/clock/st/ |
| D | st,quadfs.txt | 30 an empty string then no clock will be created for the
32 4 strings are provided then no clocks will be created
|
| /Documentation/driver-api/ |
| D | vfio-mediated-device.rst | 93 * @probe: called when new device created
127 used to trigger the creation of a mdev_device. The created mdev_device will be
134 Which will unbind and destroy all the created mdevs and remove the sysfs files.
192 The [<type-id>] name is created by adding the device driver string as a prefix
200 This attribute shows which device API is being created, for example,
206 created.
211 created.
246 Mediated devices can be created and assigned at runtime. The procedure to hot
|
| /Documentation/admin-guide/sysctl/ |
| D | user.rst | 25 the user in the user namespace who created the object and
29 who created user namespaces the creation of the object happens
33 This recursive counting of created objects ensures that creating a
|
| /Documentation/userspace-api/ |
| D | iommufd.rst | 24 small letter (iommufd) refers to the file descriptors created via /dev/iommu for
85 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can
90 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI
97 3. IOMMUFD_OBJ_HW_PAGETABLE is created when an external driver calls the IOMMUFD
101 new pagetable object and iommu_domain is created. Successful completion of
127 - Automatic domain - refers to an iommu domain created automatically when
|
| /Documentation/core-api/ |
| D | kobject.rst | 34 what happens to the kobject when it is created and destroyed.
123 The ktype is required for a kobject to be created properly, as every kobject
170 announce to the world that it has been created. This can be done with a
181 below), the uevent for **KOBJ_REMOVE** will be automatically created by the
207 the kernel will contain a run-time check for kobjects that are created
222 exception where a single kobject should be created. To create such an
237 Both types of attributes used here, with a kobject that has been created
239 special custom attribute is needed to be created.
250 kobject when its reference count reaches zero. The code which created the
259 the direct control of the code which created the kobject. So that code must
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 27 region_id, that is assigned when the region is created. The region_id
91 created and ignore those created by others.
100 that is useful to the client program that created the range.
198 program that created the range. The kernel returns this
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,realview.yaml | 22 - description: ARM RealView Emulation Baseboard (HBI-0140) was created
28 (HBI-0147) was created as a development board to test ARM TrustZone,
33 (HBI-0159, HBI-0175 and HBI-0176) was created to showcase
|
| /Documentation/virt/kvm/devices/ |
| D | vfio.rst | 11 Only one VFIO instance may be created per VM. The created device
|
12345678910>>...25