Searched full:commands (Results 1 – 25 of 410) sorted by relevance
12345678910>>...17
| /Documentation/hwmon/ |
| D | pmbus-core.rst | 21 Unfortunately, while PMBus commands are standardized, there are no mandatory
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
47 PMBus commands. Auto-detection is somewhat limited, since there are simply too
49 which PMBus commands are paged and which commands are replicated across all
53 all commands can be auto-detected. The data structures in this driver can be
57 Some commands are always auto-detected. This applies to all limit commands
67 standard PMBus commands and virtual PMBus commands.
69 Standard PMBus commands
72 Standard PMBus commands (commands values 0x00 to 0xff) are defined in the PMBUs
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-cec-error-inj | 6 The CEC Framework allows for CEC error injection commands through
8 through which the error injection commands can be given.
16 It is up to the driver to decide what commands to implement. The only
19 commands.
23 commands.
34 Drivers that implement this functionality must document the commands as
|
| /Documentation/i2c/ |
| D | i2c-stub.rst | 9 types of SMBus commands: write quick, (r/w) byte, (r/w) byte data, (r/w)
13 driver, which will then only react to SMBus commands to these addresses.
16 quick commands to the specified addresses; it will respond to the other
17 commands (also to the specified addresses) by reading from or writing to
29 SMBus block commands must be written to configure an SMBus command for
30 SMBus block operations. Writes can be partial. Block read commands always
50 Functionality override, to disable some commands. See I2C_FUNC_*
53 commands.
|
| D | functionality.rst | 22 I2C_FUNC_I2C Plain i2c-level commands (Pure SMBus
47 and write_byte commands
49 and write_byte_data commands
51 and write_word_data commands
53 and write_block_data commands
55 and write_i2c_block_data commands
56 I2C_FUNC_SMBUS_EMUL Handles all SMBus commands that can be
|
| /Documentation/firmware-guide/acpi/ |
| D | aml-debugger.rst | 25 the following commands::
41 started by using the following commands::
48 debugger commands.
50 The commands are documented in the "ACPICA Overview and Programmer Reference"
55 The detailed debugger commands reference is located in Chapter 12 "ACPICA
62 the "quit" or "exit" commands. When finished, unload the module with::
|
| /Documentation/scsi/ |
| D | ChangeLog.ips | 6 - Add Extended DCDB Commands for Tape Support in 5I
35 - Don't Issue Internal FFDC Command if there are Active Commands
95 3.60.00 - Bump max commands to 128 for use with ServeRAID
103 0.99.05 - Fix an oops on certain passthru commands
111 - Make sure passthru commands get woken up if we run out of
113 - Send all of the commands on the queue at once rather than
|
| D | ufs.rst | 68 UFS supports a subset of SCSI commands defined by SPC-4 and SBC-3.
71 It handles SCSI commands supported by UFS specification.
78 device power management operations and commands to Interconnect
94 set layer (UCS) to transport commands.
109 * UIO_SAP: To issue commands to Unipro layers.
125 and prepares the controller to transfer commands/responses between
131 Transfer request handling module of UFSHCD receives SCSI commands
147 with the SCSI Midlayer. Examples of some of the error handling commands
|
| D | scsi_eh.rst | 13 [1] How SCSI commands travel through the midlayer and to EH
30 1. How SCSI commands travel through the midlayer and to EH
56 For all non-EH commands, scsi_done() is the completion callback. It
108 for commands for which the SCSI_EH_ABORT_SCHEDULED flag is set (this
149 SCSI EH thread can expect that all in-flight commands have failed and
205 commands. A scmd is said to be recovered if the scmd is forgotten by
210 severity. Some actions are performed by issuing SCSI commands and
240 - EH reuses failed scmds to issue commands for recovery. For
242 before reusing it for EH commands.
320 (!SCSI_EH_CANCEL_CMD) commands without valid sense data. Most
[all …]
|
| D | tcm_qla2xxx.rst | 19 Use this attribute to control the discarding of SCSI commands to a
26 will discard the commands for that host.
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 14 to HCI commands and events.
21 they are translated in a sequence of HCI commands sent to the HCI layer in the
22 host controller (the chip). Commands can be executed synchronously (the sending
30 - one for executing commands : nfc_hci_msg_tx_work(). Only one command
32 - one for dispatching received events and commands : nfc_hci_msg_rx_work().
50 This is consistent with the driver need to send commands to proprietary gates
93 that must be performed using HCI commands.
107 - im_transceive() must be implemented by the driver if proprietary HCI commands
109 commands, others can be written to using the standard HCI commands. The driver
211 Serializes execution of HCI commands.
[all …]
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 28 TPM commands using the character device and the emulator will receive the
29 commands via the file descriptor and use it for sending back responses.
41 to the TPM. All commands from the driver can be read from the file descriptor
42 returned by the ioctl. The commands should be responded to immediately.
|
| /Documentation/networking/device_drivers/ethernet/huawei/ |
| D | hinic.rst | 58 Application Programmable Interface commands(API CMD) - Interface for sending
59 MGMT commands to the card. (hinic_hw_api_cmd.c, hinic_hw_api_cmd.h)
62 commands to the card and receives notifications from the MGMT modules on the
77 Command Queues(CMDQ) - The queues for sending commands for IO management and is
78 used to set the QPs addresses in HW. The commands completion events are
101 Port Commands - Send commands to the HW device for port management
|
| /Documentation/driver-api/cxl/ |
| D | maturity-map.rst | 120 Mailbox commands
125 * [1] :ref:`Background commands <background-commands>`
127 * [3] Security commands
195 .. _background-commands:
197 * **Background commands**: The CXL background command mechanism is
199 various commands. A `cancel on conflict
202 of priority commands.
|
| /Documentation/driver-api/ |
| D | libata.rst | 127 Allow low-level driver to filter ATA PACKET commands, returning a status
185 typically raid controllers that use ATA commands but do not actually do
382 Origins of commands
392 libata commands can originate from two sources - libata itself and SCSI
393 midlayer. libata internal commands are used for initialization and error
394 handling. All normal blk requests and commands for SCSI emulation are
395 passed as SCSI commands through queuecommand callback of SCSI host
398 How commands are issued
401 Internal commands
406 used by normal SCSI translated commands and ``qc->waiting`` is the
[all …]
|
| D | ioctl.rst | 7 commands and can be passed through character devices, block devices as
23 ioctl commands that follow modern conventions: ``_IO``, ``_IOR``,
24 ``_IOW``, and ``_IOWR``. These should be used for all new commands,
30 (_IOR), or both (_IOWR). _IO can indicate either commands with no
32 It is recommended to only use _IO for commands without arguments,
56 commands with different interpretations of the argument.
58 This is generally a bad idea, since changes to existing commands tend
68 ioctl commands can return negative error codes as documented in errno(3);
80 commands. As all subsystems are now responsible for handling compat
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 193 Commands: Requests, Responses, and Events
196 Commands are sent as payload inside a data frame. Currently, this is the
217 - Type of the payload. For commands always ``0x80``.
225 - Target ID for commands/messages.
229 - Source ID for commands/messages.
246 Command-type payloads are used by the host to send commands and requests to
252 Commands and events are uniquely identified by their target category
257 commands have an instance ID (``IID``), which is used to differentiate
272 response. Not all commands produce a response, and this is not detectable by
315 commands (ACKed frame but no command response) has been observed. For five
[all …]
|
| /Documentation/target/ |
| D | tcmu-design.rst | 44 SCSI commands ("fabrics"), the Linux kernel target, LIO, also modularizes
104 (mailbox); a lockless producer/consumer circular buffer for commands
110 memory-mapped layout designed for SCSI commands. Using UIO also
128 userspace (respectively) to put commands on the ring, and indicate
129 when the commands are completed.
154 Commands are placed on the ring by the kernel incrementing
159 cmd_tail, the ring is empty -- no commands are currently waiting to be
162 TCMU commands are 8-byte aligned. They start with a common header
176 buffers. For bidirectional commands, iov_cnt specifies how many iovec
190 still process the commands in the same order it appeared in the command
[all …]
|
| /Documentation/tee/ |
| D | amd-tee.rst | 45 CPU to PSP mailbox register to submit commands to the PSP. The format of the
46 command buffer is opaque to the ASP driver. It's role is to submit commands to
51 The command buffer format for the different TEE commands can be found in [2].
53 The TEE commands supported by AMD-TEE Trusted OS are:
80 a session, invoking commands and closing session with TA.
|
| /Documentation/admin-guide/ |
| D | btmrvl.rst | 5 All commands are used via debugfs interface.
13 These commands are used to configure the host sleep parameters::
35 These commands are used to enable/disable auto sleep mode
54 These commands are used to enable host sleep or wake up firmware
|
| /Documentation/driver-api/i3c/ |
| D | protocol.rst | 48 set of commands. If it has a static address (also called legacy I2C address),
121 I3C CCC commands
124 CCC (Common Command Code) commands are meant to be used for anything that is
127 CCC commands contain an 8-bit CCC ID describing the command that is executed.
134 accesses only apply to unicast commands.
141 Note that vendors can use a dedicated range of CCC IDs for their own commands
157 I3C HDR commands
160 HDR commands should be used for anything that is device specific and requires
|
| /Documentation/core-api/ |
| D | netlink.rst | 15 Older families often define "null" attributes and commands with value
33 Older families do not reply to all of the commands, especially NEW / ADD
34 commands. User only gets information whether the operation succeeded or
39 Specifically NEW and ADD commands should reply with information identifying
|
| /Documentation/block/ |
| D | pr.rst | 11 This document gives a general overview of the support ioctl commands.
13 Commands standard, specifically the section on Reservations and the
14 "PERSISTENT RESERVE IN" and "PERSISTENT RESERVE OUT" commands.
78 IOC_PR_REGISTER_IGNORE, IOC_PR_PREEMPT or IOC_PR_PREEMPT_ABORT commands.
|
| /Documentation/networking/ |
| D | phy-link-topology.rst | 16 through the legacy ioctls and the ethtool netlink commands. The base assumption
25 Commands that needs to configure the PHY will go through the net_device.phydev
65 commands.
100 There exist a set of netlink commands to query the link topology from userspace,
111 ``ETHTOOL_A_HEADER_PHY_INDEX`` field in the following ethnl commands :
|
| /Documentation/filesystems/smb/ |
| D | ksmbd.rst | 30 processing of SMB requests(commands) from clients as well as allowing for new
33 thread can decide to pass through the commands to the user space (ksmbd.mountd),
34 currently DCE/RPC commands are identified to be handled through the user space.
35 To further utilize the linux kernel, it has been chosen to process the commands
41 ownership of receiving/parsing of SMB commands. Each received command is worked
42 in parallel i.e., there can be multiple client commands which are worked in
47 performance by handling client commands in parallel.
|
| /Documentation/driver-api/media/ |
| D | dtv-core.rst | 14 - A tuner driver that implements the logic which commands the part of
20 commands the digital TV decoding hardware. The output of a demod is
|
12345678910>>...17