| /kernel/linux/linux-6.6/include/linux/ |
| D | tracefs.h | 28 * @name: The name of the file that is to be created
30 * @data: data to pass to the created file ops
31 * @fops: the file operations of the created file
33 * The evetnfs files are dynamically created. The struct eventfs_entry array
43 * created.
45 * If a file is to be created, then @mode should be populated with the file
46 * mode (permissions) for which the file is created for. This would be
47 * used to set the created inode i_mode field.
68 * struct eventfs_entry - dynamically created eventfs file call back handler
70 * @callback: The callback to get the fops of the file when it is created
|
| /kernel/liteos_a/kernel/include/ |
| D | los_swtmr.h | 113 * Software timer error code: The software timer is not created.
163 * Software timer error code: The software timer queue fails to be created.
167 * Solution: Check whether more memory can be allocated to the queue to be created.
173 * Software timer error code: The software timer task fails to be created.
219 * Software timer error code: The software sortlink fails to be created.
290 * <li>The specific timer must be created first</li>
293 * @param swtmrID [IN] Software timer ID created by LOS_SwtmrCreate. The value of ID should be in
297 * @retval #LOS_ERRNO_SWTMR_NOT_CREATED The software timer is not created.
314 * <li>The specific timer should be created and started firstly.</li>
317 * @param swtmrID [IN] Software timer ID created by LOS_SwtmrCreate. The value of ID should be in
[all …]
|
| D | los_queue.h | 77 * in the queue to be created.
83 * Queue error code: The size of the biggest message in the created queue is too big.
87 * Solution: Change the size of the biggest message in the created queue.
93 * Queue error code: The upper limit of the number of created queues is exceeded.
154 * Queue error code: The queue is not created.
363 * @param queueID [OUT] ID of the queue control structure that is successfully created.
367 * @retval #LOS_OK The message queue is successfully created.
368 …* @retval #LOS_ERRNO_QUEUE_CB_UNAVAILABLE The upper limit of the number of created queues is …
393 * <li>The specific queue should be created firstly.</li>
403 * @param queueID [IN] Queue ID created by LOS_QueueCreate. The value range is
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_encoder.h | 117 * Returns: Pointer to newly created drm encoder
126 * @drm_enc: Pointer to previously created drm encoder structure
133 * @drm_enc: Pointer to previously created drm encoder structure
139 * @drm_enc: Pointer to previously created drm encoder structure
148 * @drm_enc: Pointer to previously created drm encoder structure
155 * @drm_enc: Pointer to previously created drm encoder structure
162 * @drm_enc: Pointer to previously created drm encoder structure
168 * @drm_enc: Pointer to previously created drm encoder structure
175 * @drm_enc: Pointer to previously created drm encoder structure
181 * @drm_enc: Pointer to previously created drm encoder structure
[all …]
|
| /kernel/liteos_m/kernel/include/ |
| D | los_swtmr.h | 112 * Software timer error code: The software timer is not created.
162 * Software timer error code: The software timer queue fails to be created.
166 * Solution: Check whether more memory can be allocated to the queue to be created.
172 * Software timer error code: The software timer task fails to be created.
297 * <li>The specific timer must be created first</li>
300 * @param swtmrID [IN] Software timer ID created by LOS_SwtmrCreate.
303 * @retval #LOS_ERRNO_SWTMR_NOT_CREATED The software timer is not created.
320 * <li>The specific timer should be created and started firstly.</li>
323 * @param swtmrID [IN] Software timer ID created by LOS_SwtmrCreate.
326 * @retval #LOS_ERRNO_SWTMR_NOT_CREATED The software timer is not created.
[all …]
|
| D | los_queue.h | 78 * in the queue to be created.
84 * Queue error code: The size of the biggest message in the created queue is too big.
88 * Solution: Change the size of the biggest message in the created queue.
94 * Queue error code: The upper limit of the number of created queues is exceeded.
155 * Queue error code: The queue is not created.
387 * @param queueID [OUT] ID of the queue control structure that is successfully created.
391 * @retval #LOS_OK The message queue is successfully created.
392 …* @retval #LOS_ERRNO_QUEUE_CB_UNAVAILABLE The upper limit of the number of created queues …
420 * @param queueID [OUT] ID of the queue control structure that is successfully created.
425 * @retval #LOS_OK The message queue is successfully created.
[all …]
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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-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",
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/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
|
| /kernel/liteos_a/compat/posix/src/ |
| D | pthread.c | 171 LosTaskCB *taskCB, _pthread_data *created) in SetPthreadDataAttr() argument
173 created->attr = *userAttr; in SetPthreadDataAttr()
174 created->id = threadID; in SetPthreadDataAttr()
175 created->task = taskCB; in SetPthreadDataAttr()
176 created->state = (userAttr->detachstate == PTHREAD_CREATE_JOINABLE) ? in SetPthreadDataAttr()
179 created->cancelstate = PTHREAD_CANCEL_ENABLE; in SetPthreadDataAttr()
180 created->canceltype = PTHREAD_CANCEL_DEFERRED; in SetPthreadDataAttr()
181 created->cancelbuffer = NULL; in SetPthreadDataAttr()
182 created->canceled = 0; in SetPthreadDataAttr()
183 created->freestack = 0; /* no use default : 0 */ in SetPthreadDataAttr()
[all …]
|
| /kernel/linux/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().
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_property.h | 68 * Properties are created by one of the special functions, as explained in
100 * range. The range is unsigned. Range properties are created using
106 * range. The range is signed. Range properties are created using
115 * properties are created using drm_property_create_enum().
121 * by the property. Bitmask properties are created using
130 * enforced by the core. Object properties are created using
139 * The binary blobs are created as KMS standalone objects, and blob
141 * object. Blob properties are created by calling
144 * Actual blob objects to contain blob data are created using
214 * drm_property_blob_put(). They are created using drm_property_create_blob().
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/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()
|
| /kernel/linux/linux-6.6/include/uapi/linux/ |
| D | amt.h | 29 * AMT interface is created as Gateway mode, this attribute is used
31 * AMT interface is created as Relay mode, this attribute is used
36 * AMT interface is created as Gateway mode, this attribute is used
38 * AMT interface is created as Relay mode, this attribute is not used.
|
| /kernel/linux/linux-6.6/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
356 The group is where child config_items are created. For a subsystem,
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|