/linux/drivers/cdx/ |
H A D | cdx.h | 15 * @cdx: CDX controller associated with the device 16 * @parent: Associated CDX Bus device 25 * @req_id: Requestor ID associated with CDX device 28 * @msi_dev_id: MSI device ID associated with CDX device 67 * by caller. It also creates and registers an associated 69 * @dev_params: device parameters associated with the device to be created. 78 * also registers an associated Linux generic device. 79 * @cdx: Associated CDX controller 82 * Return: associated Linux generic device pointer on success or NULL on failure.
|
/linux/Documentation/userspace-api/media/v4l/ |
H A D | pixfmt-compressed.rst | 70 In addition, metadata associated with the frame to decode are 76 :ref:`associated Codec Control IDs <v4l2-codec-stateless-h264>`. 121 Metadata associated with the frame to decode is required to be passed 126 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-mpeg2>`. 165 Metadata associated with the frame to decode is required to be passed 167 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-vp8>`. 187 Metadata associated with the frame to decode is required to be passed 190 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-vp9>`. 215 Metadata associated with the frame to decode is required to be passed 220 See the :ref:`associated Codec Control IDs <v4l2-codec-stateless-hevc>`. [all …]
|
/linux/Documentation/networking/ |
H A D | mac80211-auth-assoc-deauth.txt | 19 else associated 49 alt authenticated or associated 62 mac80211->driver: sta_state(AP, associated) 70 mac80211->driver: bss_info_changed(QoS, HT, associated with AID) 71 mac80211->userspace: associated 73 note left of userspace: associated now 88 mac80211->driver: sta_state(AP,associated) 93 mac80211->driver: bss_info_changed(clear BSSID, not associated, no QoS, ...)
|
/linux/include/rdma/ |
H A D | rdma_cm.h | 17 * Upon receiving a device removal event, users must destroy the associated 137 * @event_handler: User callback invoked to report events associated with the 139 * @context: User specified context associated with the id. 141 * @qp_type: type of queue pair associated with the id. 159 * asynchronous operations associated with the id. 165 * associated RDMA device, if needed. 211 * rdma_destroy_qp - Deallocate the QP associated with the specified RDMA 214 * Users must destroy any QP associated with an RDMA identifier before 222 * @id: Communication identifier associated with the QP attributes to 286 * rdma_disconnect - This function disconnects the associated QP and [all …]
|
H A D | ib_cm.h | 275 * @cm_id: Communication identifier associated with the reported event. 306 * @device: Device associated with the cm_id. All related communication will 307 * be associated with the specified device. 309 * @context: User specified context associated with the communication 337 * @cm_id: Connection identifier associated with the listen request. 375 * @cm_id: Connection identifier that will be associated with the 400 * @cm_id: Connection identifier that will be associated with the 411 * @cm_id: Connection identifier associated with the connection request. 423 * @cm_id: Connection identifier associated with the connection being 435 * @cm_id: Connection identifier associated with the connection being [all …]
|
H A D | iw_cm.h | 39 * @cm_id: The IW CM identifier associated with the event. 50 * @cm_id: The IW CM identifier associated with the event. 100 * @event_handler: User callback invoked to report events associated with the 102 * @context: User specified context associated with the id. 133 * @cm_id: The IW CM identifier associated with the connection request. 149 * @cm_id: Connection identifier associated with the request. 189 * associated with a IW CM identifier. 191 * @cm_id: The IW CM identifier associated with the QP
|
/linux/include/crypto/ |
H A D | aead.h | 3 * AEAD: Authenticated Encryption with Associated Data 18 * DOC: Authenticated Encryption With Associated Data (AEAD) Cipher API 35 * associated data memory location before performing the encryption or 46 * associated data || plaintext or ciphertext. 53 * used to verify the integrity of the plaintext and the associated data. 59 * the associated data, even though it won't be written to. This makes the 61 * "destination" associated data to alias the "source" associated data. 65 * associated data, the first element must point to the plaintext/ciphertext. 69 * of the associated data buffer must contain a second copy of the IV. This is 73 * treat the IV as associated data; nevertheless the length passed to [all …]
|
/linux/kernel/trace/ |
H A D | tracing_map.c | 32 * @i: The index of the given sum associated with the tracing_map_elt 35 * Add n to sum i associated with the specified tracing_map_elt 47 * @i: The index of the given sum associated with the tracing_map_elt 49 * Retrieve the value of the sum i associated with the specified 54 * Return: The sum associated with field i for elt. 64 * @i: The index of the given variable associated with the tracing_map_elt 67 * Assign n to variable i associated with the specified tracing_map_elt 80 * @i: The index of the given variable associated with the tracing_map_elt 94 * @i: The index of the given variable associated with the tracing_map_elt 96 * Retrieve the value of the variable i associated with the specified [all …]
|
/linux/drivers/infiniband/ulp/srpt/ |
H A D | ib_srpt.h | 199 * @recv_ioctx: Receive I/O context associated with this send I/O context. 252 * @nexus: I_T nexus this channel is associated with. 255 * @ib_cm.cm_id: IB CM ID associated with the channel. 257 * @rdma_cm.cm_id: RDMA CM ID associated with the channel. 288 * @sess: Session information associated with this SRP channel. 366 * @sport_id: Port name this TPG is associated with. 369 * Zero or more target portal groups are associated with each port name 370 * (srpt_port_id). With each TPG an ACL list is associated. 381 * @tpg_list: TPGs associated with the RDMA port name. 382 * @wwn: WWN associated with the RDMA port name. [all …]
|
/linux/drivers/md/dm-vdo/indexer/ |
H A D | indexer.h | 21 * deduplicating storage, the names are generally hashes of data blocks and the associated data is 25 * associated with each name can be any 16-byte value. 29 * and save any associated index. 37 * associated with that name will be discarded. 39 * A UDS_QUERY request will return the data associated with the provided name, if any. The entry 43 * associated with the provided name, that data is returned. If there is no existing association, 44 * the name is associated with the newly provided data. This request is equivalent to a UDS_QUERY 47 * A UDS_QUERY_NO_UPDATE request will return the data associated with the provided name, but will 51 * A UDS_DELETE request removes any data associated with the provided name. This operation is 255 /* The existing data associated with the request name, if any */ [all …]
|
/linux/Documentation/driver-api/usb/ |
H A D | anchors.rst | 25 Once it has no more URBs associated with it, the anchor can be 35 all URBs associated with an anchor. 44 This function kills all URBs associated with an anchor. The URBs 52 This function unlinks all URBs associated with an anchor. The URBs 67 This function waits for all URBs associated with an anchor to finish 74 Returns true if no URBs are associated with an anchor. Locking
|
/linux/drivers/iio/ |
H A D | iio_core_trigger.h | 11 * @indio_dev: iio_dev associated with the device that will consume the trigger 19 * @indio_dev: iio_dev associated with the device that consumed the trigger 33 * @indio_dev: iio_dev associated with the device that will consume the trigger 42 * @indio_dev: iio_dev associated with the device that consumed the trigger
|
/linux/Documentation/devicetree/bindings/arm/ |
H A D | arm,coresight-cti.yaml | 96 Handle to cpu this CTI is associated with. 111 defines a phandle reference to an associated CoreSight trace device. 112 When the associated trace device is enabled, then the respective CTI 114 arm,coresight-cti-v8-arch used. If the associated device has not been 116 later resolution. If the associated device is not a CoreSight device or 145 Handle to cpu this trigger connection is associated with. 150 defines a phandle reference to an associated CoreSight trace device. 151 When the associated trace device is enabled, then the respective CTI 152 will be enabled. If the associated device has not been registered 154 resolution. If the associated device is not a CoreSight device or
|
/linux/drivers/virt/nitro_enclaves/ |
H A D | ne_misc_dev.c | 424 * @kp : NE kernel parameter associated with the NE CPU pool. 472 * @ne_enclave : Private data associated with the current enclave. 517 * @ne_enclave : Private data associated with the current enclave. 565 * @ne_enclave : Private data associated with the current enclave. 617 * core associated with the provided vCPU. 618 * @vcpu_id: Provided vCPU id to get its associated core id. 644 * @ne_enclave : Private data associated with the current enclave. 677 * associated with the vCPU and keep track of all the threads in the in ne_check_cpu_in_cpu_pool() 695 * ne_add_vcpu_ioctl() - Add a vCPU to the slot associated with the current 697 * @ne_enclave : Private data associated with the current enclave. [all …]
|
/linux/Documentation/mm/ |
H A D | hugetlbfs_reserv.rst | 69 associated with the mapping. 144 The mapping may be associated with a subpool. If so, the subpool is consulted 165 was adjusted, then the reservation map associated with the mapping is 172 reservation map associated with the mapping will be modified as required to 180 Reservations are consumed when huge pages associated with the reservations 201 If a reservation does not exist, and there is a subpool associated with the 217 The free lists associated with the memory policy of the VMA are searched for 220 associated with the page, the following adjustments are made:: 236 value of the subpool associated with the page if it exists. This will be used 277 be the case if the page was associated with a subpool that contained [all …]
|
/linux/Documentation/ABI/stable/ |
H A D | firewire-cdev | 14 Each /dev/fw* is associated with one IEEE 1394 node, which can 18 - The 1394 node which is associated with the file: 50 operations are restricted to /dev/fw* files that are associated 57 A /dev/fw* file remains associated with one particular node 102 Besides stopping and freeing I/O contexts that were associated
|
/linux/security/integrity/ima/ |
H A D | ima_iint.c | 19 * ima_iint_find - Return the iint associated with an inode 22 * Return the IMA integrity information (iint) associated with an inode, if the 83 * ima_inode_get - Find or allocate an iint associated with an inode 86 * Find an iint associated with an inode, and allocate a new one if not found. 115 * Free the IMA data associated with an inode.
|
/linux/net/tipc/ |
H A D | name_distr.c | 60 * @net: the associated network namespace 85 * @net: the associated network namespace 115 * @net: the associated network namespace 144 * @net: the associated network namespace 202 * @net: the associated network namespace 227 * tipc_publ_purge - remove publication associated with a failed node 228 * @net: the associated network namespace 271 * @net: the associated network namespace 359 * @net: the associated network namespace 390 * @net: the associated network namespace
|
/linux/Documentation/hwmon/ |
H A D | dme1737.rst | 133 Each voltage input has associated min and max limits which trigger an alarm 151 Each temperature input has associated min and max limits which trigger an alarm 161 fan tachometers. All 6 inputs have an associated min limit which triggers an 173 This chip features 5 PWM outputs. PWM outputs 1-3 are associated with fan 174 inputs 1-3 and PWM outputs 5-6 are associated with fan inputs 5-6. PWM outputs 184 defines how fast the PWM output is adjusting to changes of the associated 209 to auto_point2_pwm if the temperature of the associated zone is between 218 based on the temperature of the associated thermal zone: 256 associated min-max range, 0 otherwise. 266 input is or went outside the associated [all …]
|
/linux/drivers/media/test-drivers/vidtv/ |
H A D | vidtv_bridge.h | 39 * @dmx_fe: The frontends associated with the demux. 40 * @i2c_adapter: The i2c_adapter associated with the bridge driver. 41 * @i2c_client_demod: The i2c_clients associated with the demodulator modules. 42 * @i2c_client_tuner: The i2c_clients associated with the tuner modules.
|
/linux/scripts/kconfig/ |
H A D | expr.h | 122 /* config entries associated with this symbol */ 162 /* A property represent the config options that can be associated 179 P_COMMENT, /* text associated with a comment */ 180 P_MENU, /* prompt associated with a menu or menuconfig symbol */ 193 struct menu *menu; /* the menu the property are associated with 238 * The symbol associated with the menu node. Choices are implemented as 248 * The prompt associated with the node. This holds the prompt for a 269 /* Any help text associated with the node */
|
/linux/Documentation/devicetree/bindings/bus/ |
H A D | st,stm32mp25-rifsc.yaml | 19 - RISC registers associated with RISUP logic (resource isolation device unit 22 - RIMC registers: associated with RIMU logic (resource isolation master 28 - RISC registers associated with RISAL logic (resource isolation device unit 60 Contains the firewall ID associated to the peripheral.
|
/linux/include/linux/soc/qcom/ |
H A D | llcc-qcom.h | 136 * struct llcc_drv_data - Data associated with the llcc driver 137 * @regmaps: regmaps associated with the llcc device 138 * @bcast_regmap: regmap associated with llcc broadcast OR offset 139 * @bcast_and_regmap: regmap associated with llcc broadcast AND offset 142 * @lock: mutex associated with each slice
|
/linux/kernel/gcov/ |
H A D | fs.c | 44 * @links: associated symbolic links 49 * the actual synthesized data file plus any associated symbolic links which 93 * @info: associated profiling data 251 * Return a profiling data set associated with the given node. This is 253 * all associated object files have been unloaded. 265 * all profiling data associated with the given node. 300 * profiling data sets associated with one node simple. in gcov_seq_open() 345 * Find a node by the associated data file name. Needs to be called with 363 * Reset all profiling data associated with the specified node. 379 * corresponding file. If all associated object files have been unloaded, [all …]
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | DSD-properties-rules.rst | 16 packages associated with them and makes those data available to device drivers 20 specific type) associated with it. 28 It also may be regarded as the definition of a key and the associated data type 38 associated with an additional key (name) allowing the subset to be referred 60 associated with the Device Properties UUID.
|