Searched full:associated (Results 1 – 25 of 7087) sorted by relevance
12345678910>>...284
| /kernel/linux/linux-6.6/Documentation/networking/ |
| 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, ...)
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| 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, ...)
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| /kernel/linux/linux-5.10/include/rdma/ |
| D | rdma_cm.h | 17 * Upon receiving a device removal event, users must destroy the associated
126 * @event_handler: User callback invoked to report events associated with the
128 * @context: User specified context associated with the id.
130 * @qp_type: type of queue pair associated with the id.
148 * asynchronous operations associated with the id.
154 * associated RDMA device, if needed.
200 * rdma_destroy_qp - Deallocate the QP associated with the specified RDMA
203 * Users must destroy any QP associated with an RDMA identifier before
211 * @id: Communication identifier associated with the QP attributes to
275 * rdma_disconnect - This function disconnects the associated QP and
[all …]
|
| D | ib_cm.h | 275 * @cm_id: Communication identifier associated with the reported event.
307 * @device: Device associated with the cm_id. All related communication will
308 * be associated with the specified device.
310 * @context: User specified context associated with the communication
338 * @cm_id: Connection identifier associated with the listen request.
379 * @cm_id: Connection identifier that will be associated with the
404 * @cm_id: Connection identifier that will be associated with the
415 * @cm_id: Connection identifier associated with the connection request.
427 * @cm_id: Connection identifier associated with the connection being
439 * @cm_id: Connection identifier associated with the connection being
[all …]
|
| 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.
99 * @event_handler: User callback invoked to report events associated with the
101 * @context: User specified context associated with the id.
130 * iw_cm_get_qp - Return the ib_qp associated with a QPN
153 * @cm_id: The IW CM identifier associated with the connection request.
169 * @cm_id: Connection identifier associated with the request.
209 * associated with a IW CM identifier.
211 * @cm_id: The IW CM identifier associated with the QP
|
| /kernel/linux/linux-6.6/include/rdma/ |
| 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 …]
|
| 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 …]
|
| 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
|
| /kernel/linux/linux-6.6/drivers/scsi/cxlflash/ |
| D | lunmgt.c | 26 * @sdev: SCSI device associated with LUN.
54 * @sdev: SCSI device associated with LUN.
79 * @cfg: Internal structure associated with the host.
80 * @wwid: WWID associated with LUN.
97 * @wwid: WWID associated with LUN.
114 * @sdev: SCSI device associated with LUN.
115 * @wwid: WWID associated with LUN.
121 * The block allocation map is shared across all adapters (i.e. associated
122 * wih the global list). Since different attributes are associated with
176 * @cfg: Internal structure associated with the host.
[all …]
|
| D | ocxl_hw.c | 157 * @ctx_cookie: Adapter context associated with the process element.
286 * @ctx_cookie: Context associated with the interrupt.
464 * ocxlflash_get_context() - obtains the context associated with the host
465 * @pdev: PCI device associated with the host.
466 * @afu_cookie: Hardware AFU associated with the host.
479 * @pdev: PCI device associated with the host.
480 * @afu_cookie: Hardware AFU associated with the host.
562 * @afu_cookie: Hardware AFU associated with the host.
574 * @pdev: PCI device associated with the host.
610 * @ctx: Context associated with the request.
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/cxlflash/ |
| D | lunmgt.c | 26 * @sdev: SCSI device associated with LUN.
54 * @sdev: SCSI device associated with LUN.
79 * @cfg: Internal structure associated with the host.
80 * @wwid: WWID associated with LUN.
97 * @wwid: WWID associated with LUN.
114 * @sdev: SCSI device associated with LUN.
115 * @wwid: WWID associated with LUN.
121 * The block allocation map is shared across all adapters (i.e. associated
122 * wih the global list). Since different attributes are associated with
176 * @cfg: Internal structure associated with the host.
[all …]
|
| D | ocxl_hw.c | 156 * @ctx_cookie: Adapter context associated with the process element.
285 * @ctx_cookie: Context associated with the interrupt.
461 * ocxlflash_get_context() - obtains the context associated with the host
462 * @pdev: PCI device associated with the host.
463 * @afu_cookie: Hardware AFU associated with the host.
476 * @pdev: PCI device associated with the host.
477 * @afu_cookie: Hardware AFU associated with the host.
559 * @afu_cookie: Hardware AFU associated with the host.
571 * @pdev: PCI device associated with the host.
607 * @ctx: Context associated with the request.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/ata/ |
| D | ahci-st.txt | 8 - interrupts : Interrupt associated with the SATA device
9 - interrupt-names : Associated name must be; "hostc"
11 - clock-names : Associated name must be; "ahci_clk"
13 - phy-names : Associated name must be; "ahci_phy"
17 - reset-names : Associated names must be; "pwr-dwn", "sw-rst" and "pwr-rst"
|
| D | ahci-mtk.txt | 9 - interrupts : Interrupt associated with the SATA device.
10 - interrupt-names : Associated name must be: "hostc".
13 - clock-names : Associated names must be: "ahb", "axi", "asic", "rbc", "pm".
15 - phy-names : Associated name must be: "sata-phy".
24 - reset-names : Associated names must be: "axi", "sw", "reg".
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ata/ |
| D | ahci-st.txt | 8 - interrupts : Interrupt associated with the SATA device
9 - interrupt-names : Associated name must be; "hostc"
11 - clock-names : Associated name must be; "ahci_clk"
13 - phy-names : Associated name must be; "ahci_phy"
17 - reset-names : Associated names must be; "pwr-dwn", "sw-rst" and "pwr-rst"
|
| D | ahci-mtk.txt | 9 - interrupts : Interrupt associated with the SATA device.
10 - interrupt-names : Associated name must be: "hostc".
13 - clock-names : Associated names must be: "ahb", "axi", "asic", "rbc", "pm".
15 - phy-names : Associated name must be: "sata-phy".
24 - reset-names : Associated names must be: "axi", "sw", "reg".
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 64 In addition, metadata associated with the frame to decode are
70 :ref:`associated Codec Control IDs <v4l2-mpeg-h264>`. Exactly
115 Metadata associated with the frame to decode is required to be passed
119 See the :ref:`associated Codec Control IDs <v4l2-mpeg-mpeg2>`.
158 Metadata associated with the frame to decode is required to be passed
160 See the :ref:`associated Codec Control IDs <v4l2-mpeg-vp8>`.
198 Metadata associated with the frame to decode is required to be passed
203 See the :ref:`associated Codec Control IDs <v4l2-mpeg-hevc>`.
204 Buffers associated with this pixel format must contain the appropriate
225 See the :ref:`associated Codec Control IDs <v4l2-mpeg-fwht>`.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | generic-counter.rst | 54 A Signal may be associated with one or more Counts.
80 A counter is defined as a set of input signals associated with count
81 data that are generated by the evaluation of the state of the associated
84 each associated with a set of Signals, whose respective Synapse
86 associated Counts.
138 A Count has a set of one or more associated Synapses.
144 associated with a single Signal via a single Synapse. Take for example
158 incremented. The Signal is associated with the respective Count via a
167 many Signals may be associated with even a single Count. For example, a
184 associated with a single Count: a rising or falling edge on either A or
[all …]
|
| /kernel/linux/linux-5.10/include/crypto/ |
| D | aead.h | 3 * AEAD: Authenticated Encryption with Associated Data
16 * DOC: Authenticated Encryption With Associated Data (AEAD) Cipher API
33 * pointer to the associated data memory location before performing the
34 * encryption or decryption operation. In case of an encryption, the associated
36 * associated data memory must contain data that is used to verify the integrity
47 * associated data || plaintext or ciphertext.
57 * the associated data, even though it won't be written to. This makes the
59 * "destination" associated data to alias the "source" associated data.
63 * associated data, the first element must point to the plaintext/ciphertext.
67 * of the associated data buffer must contain a second copy of the IV. This is
[all …]
|
| /kernel/linux/linux-6.6/drivers/cdx/ |
| D | cdx.h | 15 * @cdx: CDX controller associated with the device
16 * @parent: Associated CDX controller
23 * @req_id: Requestor ID associated with CDX device
54 * by caller. It also creates and registers an associated
56 * @dev_params: device parameters associated with the device to be created.
|
| /kernel/linux/linux-6.6/include/crypto/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | ppc4xx_edac.c | 24 * associated with the IMB DDR2 ECC controller found in the AMCC/IBM
216 * Strings associated with PLB master IDs capable of being posted in
236 * This routine reads and returns the data associated with the
295 * @mci: A pointer to the EDAC memory controller instance associated
304 * driver-unique report message associated with the ECCESS[BKNER]
357 * @mci: A pointer to the EDAC memory controller instance associated
366 * driver-unique report message associated with the ECCESS[CKBER]
415 * @mci: A pointer to the EDAC memory controller instance associated
424 * driver-unique report message associated with the ECCESS[BNCE]
480 * @mci: A pointer to the EDAC memory controller instance associated
[all …]
|
| /kernel/linux/linux-6.6/drivers/edac/ |
| D | ppc4xx_edac.c | 25 * associated with the IMB DDR2 ECC controller found in the AMCC/IBM
203 * Strings associated with PLB master IDs capable of being posted in
223 * This routine reads and returns the data associated with the
282 * @mci: A pointer to the EDAC memory controller instance associated
291 * driver-unique report message associated with the ECCESS[BKNER]
344 * @mci: A pointer to the EDAC memory controller instance associated
353 * driver-unique report message associated with the ECCESS[CKBER]
402 * @mci: A pointer to the EDAC memory controller instance associated
411 * driver-unique report message associated with the ECCESS[BNCE]
467 * @mci: A pointer to the EDAC memory controller instance associated
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| 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
|
12345678910>>...284