created (full) in projects: linux-6.15 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...123

/linux-6.15/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
/linux-6.15/include/kunit/
D	device.h	`24 * @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.15/Documentation/userspace-api/
D	iommufd.rst	24 small letter (iommufd) refers to the file descriptors created via /dev/iommu for 61 feature.) As such, it must be created with a given nesting parent stage-2 69 to those events. A FAULT object must be created first to get a fault_id that 87 must be created given a nesting parent HWPT_PAGING object, and then it would 97 vIOMMU objects created for individual slices of different physical IOMMUs. 123 vIOMMU object must be created first to get its viommu_id, which could be then 187 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can 192 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI 199 3. IOMMUFD_OBJ_HWPT_PAGING can be created in two ways: 201 * IOMMUFD_OBJ_HWPT_PAGING is automatically created when an external driver [all …]
/linux-6.15/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",
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.`
/linux-6.15/drivers/net/ethernet/mellanox/mlx5/core/steering/hws/
D	mlx5hws.h	108 /* Define whether the created matcher supports resizing into a bigger matcher / 319 @ctx: The context in which the new template will be created. 411 * Both matchers must be in the same table type, must be created with the 450 * @matcher: The matcher in which the new rule will be created. 507 * @ctx: The context in which the new action will be created. 520 * @ctx: The context in which the new action will be created. 532 * @ctx: The context in which the new action will be created. 546 * @ctx: The context in which the new action will be created. 559 * @ctx: The context in which the new action will be created. 579 * @ctx: The context in which the new action will be created. [all …]
/linux-6.15/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-6.15/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.`
/linux-6.15/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-6.15/Documentation/infiniband/
D	ucaps.rst	`42 is created during the first call and subsequent calls increment the 45 The UCAP character device is created under /dev/infiniband, and its 62 is created when the first UCAP character device is created. 64 The UCAP character device is created under /dev/infiniband.`
/linux-6.15/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-6.15/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().
/linux-6.15/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-6.15/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 …]
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. 224 Symbolic links can be created with debugfs_create_symlink(). 227 there is no automatic cleanup of any directories created in debugfs. If a 240 pointer for every debugfs file they created so that all files could be
/linux-6.15/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-6.15/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.`
/linux-6.15/drivers/gpu/drm/xe/
D	xe_bo_doc.h	27 * 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
D	xe_bo_types.h	`53 * @client: @xe_drm_client which created the bo 62 * @pxp_key_instance: PXP key instance this BO was created against. A 71 /** @created: Whether the bo has passed initial creation */ 72 bool created; member`
/linux-6.15/net/sched/
D	sch_ingress.c	`83 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() 248 bool created; in clsact_init() local 257 entry = tcx_entry_fetch_or_create(dev, true, &created); in clsact_init() 262 if (created) in clsact_init() 276 entry = tcx_entry_fetch_or_create(dev, false, &created); in clsact_init() 281 if (created) in clsact_init()`
/linux-6.15/include/rdma/
D	restrack.h	`97 * There are two types of entities: created by user and created 100 * This is relevant for the entities created by users. 101 * For the entities created by kernel, this pointer will be NULL. 105 * @kern_name: name of owner for the kernel created entities.`
/linux-6.15/fs/
D	anon_inodes.c	139 * All the files created with anon_inode_getfile() will share a single inode, 141 * setup. Returns the newly created file* or an error pointer. 164 * All the files created with anon_inode_getfile() will share a single inode, 166 * setup. Allows setting the fmode. Returns the newly created file* or an error 208 * Returns the newly created file* or an error pointer. 261 * order to operate correctly. All the files created with 264 * setup. Returns a newly created file descriptor or an error code. 297 * Returns a newly created file descriptor or an error code.
/linux-6.15/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.

12 3 4 5 6 7 8 9 10 >>...123