| /linux-5.10/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-rnbd-client | 71 will be created.
112 Description: For each device mapped on the client a new symbolic link is created as
114 to the block device created by rnbd (/sys/block/rnbd<N>/).
115 The <device_id> of each device is created as follows:
|
| /linux-5.10/include/sound/ |
| D | seq_virmidi.h | 16 * This instance is created at each time the midi device file is
46 int client; /* created/attached client */
47 int port; /* created/attached port */
56 * attached sequencer port. sequencer port is not created
61 * sequencer port is created in virmidi.
|
| /linux-5.10/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
|
| /linux-5.10/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 39 entries corresponding to EPF driver will be created by the EPF core.
55 (These entries are created by the framework when any new <EPF Device> is
56 created)
76 entries corresponding to EPC device will be created by the EPC core.
90 <EPF Device>. These symbolic links should be created by the user to
96 all the EPF devices are created and linked with the EPC device.
|
| /linux-5.10/drivers/extcon/ |
| D | devres.c | 54 * @dev: the device owning the extcon device being created
91 * @dev: the device owning the extcon device being created
106 * @dev: the device owning the extcon device being created
142 * @dev: the device owning the extcon device being created
157 * @dev: the device owning the extcon device being created
201 * @dev: the device owning the extcon device being created
218 * @dev: the device owning the extcon device being created
256 * @dev: the device owning the extcon device being created
|
| /linux-5.10/include/drm/ |
| D | drm_property.h | 61 * Properties are created by one of the special functions, as explained in
93 * range. The range is unsigned. Range properties are created using
99 * range. The range is signed. Range properties are created using
108 * properties are created using drm_property_create_enum().
114 * by the property. Bitmask properties are created using
123 * enforced by the core. Object properties are created using
132 * The binary blobs are created as KMS standalone objects, and blob
134 * object. Blob properties are created by calling
137 * Actual blob objects to contain blob data are created using
207 * drm_property_blob_put(). They are created using drm_property_create_blob().
|
| /linux-5.10/drivers/hv/ |
| D | hv_debugfs.c | 67 pr_debug("debugfs_hyperv: file %s not created\n", buffer); in hv_debug_delay_files()
75 pr_debug("debugfs_hyperv: file %s not created\n", message); in hv_debug_delay_files()
94 pr_debug("debugfs_hyperv: file %s not created\n", status); in hv_debug_set_test_state()
119 pr_debug("debugfs_hyperv: hyperv/%s/ not created\n", in hv_debug_add_dev_dir()
128 pr_debug("debugfs_hyperv: hyperv/%s/%s/ not created\n", in hv_debug_add_dev_dir()
174 pr_debug("debugfs_hyperv: hyperv/ not created\n"); in hv_debug_init()
|
| /linux-5.10/drivers/greybus/ |
| D | greybus_trace.h | 127 * Occurs after a new operation is created for an outgoing request
128 * has been successfully created.
133 * Occurs after a new core operation has been created.
138 * Occurs after a new operation has been created for an incoming
139 * request has been successfully created and initialized.
199 * Occurs after a new connection is successfully created.
268 * Occurs after a new bundle is successfully created.
332 * Occurs after a new interface is successfully created.
405 * Occurs after a new module is successfully created, before
416 * Occurs after a module is successfully created, before registering
[all …]
|
| /linux-5.10/include/rdma/ |
| D | restrack.h | 82 * There are two types of entities: created by user and created
85 * This is relevant for the entities created by users.
86 * For the entities created by kernel, this pointer will be NULL.
90 * @kern_name: name of owner for the kernel created entities.
|
| /linux-5.10/Documentation/filesystems/ |
| 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
357 The group is where child config_items are created. For a subsystem,
[all …]
|
| 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 …]
|
| 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 | sharedsubtree.rst | 385 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is
387 are created and mounted at the dentry 'b' on all mounts where 'B'
389 created. This propagation tree is identical to the propagation tree of
394 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is
396 are created and mounted at the dentry 'b' on all mounts where 'B'
402 mount 'C' which is clone of 'A', is created. Its root dentry is 'a' .
404 'C3' ... are created and mounted at the dentry 'b' on all mounts where
406 'C','C1',.. 'Cn' is created. This propagation tree is identical to the
415 unbindable) mount. A new mount 'C' which is clone of 'A', is created.
419 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is
[all …]
|
| 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
|
| /linux-5.10/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
|
| /linux-5.10/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.
|
| /linux-5.10/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 …]
|
| /linux-5.10/tools/testing/selftests/net/ |
| D | reuseport_dualstack.c | 163 fprintf(stderr, "---- UDP IPv4 created before IPv6 ----\n"); in main()
170 fprintf(stderr, "---- UDP IPv6 created before IPv4 ----\n"); in main()
180 fprintf(stderr, "---- UDP IPv4 created before IPv6 (large) ----\n"); in main()
187 fprintf(stderr, "---- UDP IPv6 created before IPv4 (large) ----\n"); in main()
194 fprintf(stderr, "---- TCP IPv4 created before IPv6 ----\n"); in main()
201 fprintf(stderr, "---- TCP IPv6 created before IPv4 ----\n"); in main()
|
| /linux-5.10/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
97 directories must be created:
110 Each configuration also needs its strings, so a subdirectory must be created
127 directory must be created::
148 At this moment a number of gadgets is created, each of which has a number of
354 a number of its default sub-groups created automatically.
|
| /linux-5.10/tools/testing/selftests/efivarfs/ |
| D | efivarfs.sh | 61 echo "$file couldn't be created" >&2
80 echo "$file can not be created without writing" >&2
101 echo "$file couldn't be created" >&2
156 echo "$file could not be created" >&2
|
| /linux-5.10/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
|
| /linux-5.10/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
|
| /linux-5.10/arch/x86/kvm/mmu/ |
| D | mmutrace.h | 152 TP_PROTO(struct kvm_mmu_page *sp, bool created),
153 TP_ARGS(sp, created),
157 __field(bool, created)
162 __entry->created = created;
166 __entry->created ? "new" : "existing")
|
| /linux-5.10/arch/arm/mach-pxa/ |
| D | viper.h | 6 * Created: Feb 03, 2003
12 * Created based on lubbock.h:
14 * Created: Jun 15, 2001
|