Searched refs:responses (Results 1 – 25 of 57) sorted by relevance
123
| /linux-5.19.10/drivers/misc/ti-st/ |
| D | Kconfig | 15 to register themselves with core and send data, the responses
|
| /linux-5.19.10/arch/s390/ |
| D | Kconfig.debug | 21 and instruction responses to the CIO layer of Linux kernel. The newly created
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | debugfs-olpc | 8 reading their responses.
|
| /linux-5.19.10/Documentation/vm/ |
| D | index.rst | 35 notes and mailing list responses for elaborating descriptions of data
|
| /linux-5.19.10/Documentation/usb/ |
| D | raw-gadget.rst | 28 2. Raw Gadget allows providing arbitrary data as responses to USB requests,
31 responses to USB requests.
|
| /linux-5.19.10/Documentation/devicetree/bindings/mmc/ |
| D | mtk-sd.yaml | 131 If present, HS400 command responses are sampled on rising edges.
132 If not present, HS400 command responses are sampled on falling edges.
|
| /linux-5.19.10/Documentation/networking/ |
| D | nfc.rst | 126 commands and their responses.
129 on. In order to allow valid "empty" responses, every data received has a NULL
|
| D | mctp.rst | 169 implicit local socket address, to allow the socket to receive responses to this
173 Sockets will only receive responses to requests they have sent (with TO=1) and
212 Like the send calls, sockets will only receive responses to requests they have
|
| /linux-5.19.10/drivers/net/ethernet/sfc/siena/ |
| D | Kconfig | 43 Driver-Interface) commands and responses, allowing debugging of
|
| /linux-5.19.10/kernel/ |
| D | Kconfig.hz | 47 systems requiring fast interactive responses to events.
|
| /linux-5.19.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | ftm-initiator.c | 124 memset(mvm->ftm_initiator.responses, 0, in iwl_mvm_ftm_reset()
125 sizeof(mvm->ftm_initiator.responses)); in iwl_mvm_ftm_reset()
151 result.ftm.burst_index = mvm->ftm_initiator.responses[i]; in iwl_mvm_ftm_restart()
1280 result.ftm.burst_index = mvm->ftm_initiator.responses[peer_idx]; in iwl_mvm_ftm_range_resp()
1281 mvm->ftm_initiator.responses[peer_idx]++; in iwl_mvm_ftm_range_resp()
|
| /linux-5.19.10/drivers/net/ethernet/sfc/ |
| D | Kconfig | 63 Driver-Interface) commands and responses, allowing debugging of
|
| /linux-5.19.10/Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 29 commands via the file descriptor and use it for sending back responses.
|
| /linux-5.19.10/Documentation/scsi/ |
| D | ufs.rst | 123 and prepares the controller to transfer commands/responses between
131 controller. Also, the module decodes responses received from the UFS
|
| /linux-5.19.10/Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 246 the EC as well as by the EC to send responses and events back to the host.
247 We differentiate between requests (sent by the host), responses (sent by the
288 Furthermore, requests, responses, and events have an associated target ID
295 field, as responses are generally sent from the EC to the host).
|
| D | internal.rst | 72 responses of the EC to those requests, and events (sent from EC to host).
73 It, specifically, distinguishes events from request responses, matches
74 responses to their corresponding requests, and implements request timeouts.
77 how request responses and, especially, events are dealt with. It provides an
294 separates responses to requests from events, which are also sent by the EC
295 via a |ssh_command| payload. While responses are handled in this layer,
|
| /linux-5.19.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra30-mc.yaml | 25 Memory Crossbar, which routes request and responses between Arbitration
|
| /linux-5.19.10/Documentation/networking/devlink/ |
| D | prestera.rst | 27 - Traps ARP broadcast packets (both requests/responses)
|
| /linux-5.19.10/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | dpio-driver.rst | 45 QBman portal interface-- sends portal commands, gets responses::
|
| /linux-5.19.10/Documentation/driver-api/surface_aggregator/clients/ |
| D | dtx.rst | 103 Valid responses by a user-space daemon to a detachment request event are:
125 responses.
137 See :ref:`ioctls` for more details on these responses.
|
| /linux-5.19.10/Documentation/driver-api/mei/ |
| D | mei.rst | 116 requests up to bytes 2k and received responses up to 2k bytes).
|
| /linux-5.19.10/drivers/char/ipmi/ |
| D | Kconfig | 178 receive requests and send responses back to the BMC via
|
| /linux-5.19.10/Documentation/i2c/ |
| D | fault-codes.rst | 80 may verify the device returns *correct* responses, and
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | orangefs.rst | 473 Userspace uses writev() on /dev/pvfs2-req to pass responses to the requests
490 responses::
505 Readdir responses initialize the fifth element io_array like this::
|
| /linux-5.19.10/Documentation/admin-guide/media/ |
| D | si4713.rst | 23 The chip is programmed using commands and responses. There are also several
|
123