Home
last modified time | relevance | path

Searched full:created (Results 1 – 25 of 3334) sorted by relevance

12345678910>>...134

/linux-6.8/include/linux/
Dtracefs.h28 * @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.
66 * struct eventfs_entry - dynamically created eventfs file call back handler
68 * @callback: The callback to get the fops of the file when it is created
/linux-6.8/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_encoder.h133 * Returns: Pointer to newly created drm encoder
142 * @drm_enc: Pointer to previously created drm encoder structure
149 * @drm_enc: Pointer to previously created drm encoder structure
155 * @drm_enc: Pointer to previously created drm encoder structure
164 * @drm_enc: Pointer to previously created drm encoder structure
171 * @drm_enc: Pointer to previously created drm encoder structure
177 * @drm_enc: Pointer to previously created drm encoder structure
184 * @drm_enc: Pointer to previously created drm encoder structure
190 * @drm_enc: Pointer to previously created drm encoder structure
198 * @drm_enc: Pointer to previously created drm encoder structure
/linux-6.8/include/kunit/
Ddevice.h24 * @name: The name to give the created driver.
36 * @name: The name to give the created device.
52 * @name: The name to give the created device.
69 * @test: The test context object which created the device
72 * Unregisters and destroys a struct device which was created with
73 * kunit_device_register or kunit_device_register_with_driver. If KUnit created
/linux-6.8/Documentation/ABI/testing/
Dsysfs-bus-vfio-mdev9 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.
Dsysfs-bus-event_source-devices-hv_gpci92 * 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",
Dsysfs-class-vduse15 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.
/linux-6.8/include/sound/
Dseq_virmidi.h16 * 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-6.8/Documentation/PCI/endpoint/
Dpci-endpoint-cfs.rst39 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.
/linux-6.8/Documentation/driver-api/driver-model/
Dbinding.rst63 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-6.8/drivers/extcon/
Ddevres.c54 * @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-6.8/include/drm/
Ddrm_property.h68 * 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().
/linux-6.8/drivers/hv/
Dhv_debugfs.c67 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-6.8/Documentation/filesystems/
Dconfigfs.rst21 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 …]
Dhpfs.rst71 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 …]
Ddebugfs.rst39 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
Dsharedsubtree.rst386 which is clone of 'A', is created. Its root dentry is 'a' . 'C' is
388 are created and mounted at the dentry 'b' on all mounts where 'B'
390 created. This propagation tree is identical to the propagation tree of
395 which is clone of 'A', is created. Its root dentry is 'a'. 'C' is
397 are created and mounted at the dentry 'b' on all mounts where 'B'
403 mount 'C' which is clone of 'A', is created. Its root dentry is 'a' .
405 'C3' ... are created and mounted at the dentry 'b' on all mounts where
407 'C','C1',.. 'Cn' is created. This propagation tree is identical to the
416 unbindable) mount. A new mount 'C' which is clone of 'A', is created.
420 which is a clone of 'A' is created. Its root dentry is 'a'. 'C' is
[all …]
/linux-6.8/drivers/greybus/
Dgreybus_trace.h127 * 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-6.8/include/uapi/linux/
Damt.h29 * 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.
/linux-6.8/net/sched/
Dsch_ingress.c83 bool created; in ingress_init() local
91 entry = tcx_entry_fetch_or_create(dev, true, &created); in ingress_init()
96 if (created) in ingress_init()
247 bool created; in clsact_init() local
256 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init()
261 if (created) in clsact_init()
275 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init()
280 if (created) in clsact_init()
/linux-6.8/drivers/gpu/drm/xe/
Dxe_bo_doc.h27 * A kernel BO is created as part of driver load (e.g. uC firmware images, GuC
28 * ADS, etc...) or a BO created as part of a user operation which requires
40 * A user BO is created via the DRM_IOCTL_XE_GEM_CREATE IOCTL. Once it is
41 * created the BO can be mmap'd (via DRM_IOCTL_XE_GEM_MMAP_OFFSET) for user
50 * A private BO is a user BO created with a valid VM argument passed into the
52 * mappings can only be created for the BO within the VM it is tied to. Lastly,
59 * An external BO is a user BO created with a NULL VM argument passed into the
69 * When a user BO is created, a mask of valid placements is passed indicating
/linux-6.8/include/rdma/
Drestrack.h94 * There are two types of entities: created by user and created
97 * This is relevant for the entities created by users.
98 * For the entities created by kernel, this pointer will be NULL.
102 * @kern_name: name of owner for the kernel created entities.
/linux-6.8/Documentation/usb/
Dgadget_configfs.rst62 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.
/linux-6.8/Documentation/leds/
Duleds.rst12 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-6.8/Documentation/core-api/
Dkobject.rst34 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-6.8/include/linux/rpmsg/
Dns.h15 * @flags: indicates whether service is created or destroyed
19 * rpmsg channel (i.e device) is created/destroyed. In turn, the ->probe()
32 * @RPMSG_NS_CREATE: a new remote service was just created

12345678910>>...134