| /Linux-v5.15/net/sctp/ |
| D | sm_statefuns.c | 58 struct sctp_cmd_seq *commands);
67 struct sctp_cmd_seq *commands,
75 struct sctp_cmd_seq *commands);
82 struct sctp_cmd_seq *commands);
89 struct sctp_cmd_seq *commands);
96 struct sctp_cmd_seq *commands);
101 struct sctp_cmd_seq *commands,
111 struct sctp_cmd_seq *commands,
121 struct sctp_cmd_seq *commands);
129 struct sctp_cmd_seq *commands);
[all …]
|
| D | sm_sideeffect.c | 47 struct sctp_cmd_seq *commands,
56 struct sctp_cmd_seq *commands,
139 struct sctp_cmd_seq *commands) in sctp_gen_sack() argument
200 sctp_add_cmd_sf(commands, SCTP_CMD_TIMER_RESTART, in sctp_gen_sack()
215 sctp_add_cmd_sf(commands, SCTP_CMD_REPLY, SCTP_CHUNK(sack)); in sctp_gen_sack()
218 sctp_add_cmd_sf(commands, SCTP_CMD_TIMER_STOP, in sctp_gen_sack()
546 static void sctp_do_8_2_transport_strike(struct sctp_cmd_seq *commands, in sctp_do_8_2_transport_strike() argument
621 static void sctp_cmd_init_failed(struct sctp_cmd_seq *commands, in sctp_cmd_init_failed() argument
632 sctp_add_cmd_sf(commands, SCTP_CMD_EVENT_ULP, in sctp_cmd_init_failed()
635 sctp_add_cmd_sf(commands, SCTP_CMD_NEW_STATE, in sctp_cmd_init_failed()
[all …]
|
| /Linux-v5.15/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 …]
|
| /Linux-v5.15/include/uapi/linux/ |
| D | isst_if.h | 20 * commands. Even if the firmware is capable, driver may
22 * @max_cmds_per_ioctl: Returns the maximum number of commands driver will
29 * support and also number of commands to send in a single IOCTL request.
58 * one or more CPU mapping commands. Here IOCTL return value indicates
59 * number of commands sent or error number if no commands have been sent.
84 * struct isst_if_io_regs - structure for IO register commands
85 * @cmd_count: Number of io reg commands in io_reg[]
89 * one or more read/write commands to PUNIT. Here IOCTL return value
121 * struct isst_if_mbox_cmds - structure for mailbox commands
122 * @cmd_count: Number of mailbox commands in mbox_cmd[]
[all …]
|
| D | cxl_mem.h | 14 * Not all of all commands that the driver supports are always available for use
16 * order to determine the live set of commands.
97 * struct cxl_mem_query_commands - Query supported commands.
100 * is 0, driver will return the number of total supported commands.
102 * @commands: Output array of supported commands. This array must be allocated
105 * Allow userspace to query the available commands supported by both the driver,
106 * and the hardware. Commands that aren't supported by either the driver, or the
111 * - { .n_commands = 0 } // Get number of supported commands
112 * - { .n_commands = 15, .commands = buf } // Return first 15 (or less)
113 * supported commands
[all …]
|
| /Linux-v5.15/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/ |
| D | uncore-ddrc.json | 19 "BriefDescription": "DDRC write commands",
20 "PublicDescription": "DDRC write commands",
26 "BriefDescription": "DDRC read commands",
27 "PublicDescription": "DDRC read commands",
33 "BriefDescription": "DDRC precharge commands",
34 "PublicDescription": "DDRC precharge commands",
40 "BriefDescription": "DDRC active commands",
41 "PublicDescription": "DDRC active commands",
47 "BriefDescription": "DDRC rank commands",
48 "PublicDescription": "DDRC rank commands",
|
| /Linux-v5.15/drivers/infiniband/hw/hns/ |
| D | hns_roce_cmd.h | 40 /* QPC BT commands */
57 /* CQC BT commands */
68 /* MPT BT commands */
79 /* CQC TIMER commands */
83 /* MPT commands */
86 /* SRQC BT commands */
97 /* QPC TIMER commands */
101 /* EQC commands */
111 /* SCC CTX BT commands */
117 /* TPT commands */
[all …]
|
| /Linux-v5.15/arch/sparc/kernel/ |
| D | setup_32.c | 148 static void __init boot_flags_init(char *commands) in boot_flags_init() argument
150 while (*commands) { in boot_flags_init()
152 while (*commands == ' ') in boot_flags_init()
153 commands++; in boot_flags_init()
156 if (*commands == '\0') in boot_flags_init()
158 if (*commands == '-') { in boot_flags_init()
159 commands++; in boot_flags_init()
160 while (*commands && *commands != ' ') in boot_flags_init()
161 process_switch(*commands++); in boot_flags_init()
164 if (!strncmp(commands, "mem=", 4)) { in boot_flags_init()
[all …]
|
| /Linux-v5.15/drivers/platform/x86/ |
| D | samsung-laptop.c | 147 const struct sabi_commands commands; member
172 .commands = {
235 .commands = {
297 * This allow to call arbitrary sabi commands wihout
467 /* simple wrappers usable with most commands */
480 const struct sabi_commands *commands = &samsung->config->commands; in read_brightness() local
485 retval = sabi_command(samsung, commands->get_brightness, in read_brightness()
502 const struct sabi_commands *commands = &samsung->config->commands; in set_brightness() local
513 sabi_set_commandb(samsung, commands->set_brightness, 0); in set_brightness()
516 sabi_set_commandb(samsung, commands->set_brightness, user_level); in set_brightness()
[all …]
|
| /Linux-v5.15/tools/power/cpupower/man/ |
| D | cpupower.1 | 16 The manpages of the commands (cpupower\-<command>(1)) provide detailed
18 of supported commands.
24 Shows supported commands and general usage.
30 This option is not supported by all commands, details can be found in the
31 manpages of the commands.
33 Some commands access all cores (typically the *\-set commands), some only
34 the first core (typically the *\-info commands) by default.
|
| /Linux-v5.15/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.
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| D | uncore-memory.json | 134 "BriefDescription": "DRAM Page Activate commands sent due to a write request",
139 …ounts DRAM Page Activate commands sent on this channel due to a write request to the iMC (Memory C…
144 "BriefDescription": "All DRAM CAS Commands issued",
149 …ption": "Counts all CAS (Column Address Select) commands issued to DRAM per memory channel. CAS c…
154 "BriefDescription": "All DRAM Read CAS Commands issued (does not include underfills)",
159 …ounts CAS (Column Access Select) regular read commands issued to DRAM on a per channel basis. CAS…
164 "BriefDescription": "DRAM Underfill Read CAS Commands issued",
169 …umn Access Select) underfill read commands issued to DRAM due to a partial write, on a per channel…
174 …"BriefDescription": "DRAM CAS (Column Address Strobe) Commands.; DRAM WR_CAS (w/ and w/out auto-pr…
179 …"PublicDescription": "Counts the total number or DRAM Write CAS commands issued on this channel wh…
[all …]
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-memory.json | 68 "BriefDescription": "DRAM Page Activate commands sent due to a write request",
73 …ounts DRAM Page Activate commands sent on this channel due to a write request to the iMC (Memory C…
78 "BriefDescription": "All DRAM CAS Commands issued",
83 …ption": "Counts all CAS (Column Address Select) commands issued to DRAM per memory channel. CAS c…
88 "BriefDescription": "All DRAM Read CAS Commands issued (does not include underfills)",
93 …ounts CAS (Column Access Select) regular read commands issued to DRAM on a per channel basis. CAS…
98 "BriefDescription": "DRAM Underfill Read CAS Commands issued",
103 …umn Access Select) underfill read commands issued to DRAM due to a partial write, on a per channel…
108 …"BriefDescription": "DRAM CAS (Column Address Strobe) Commands.; DRAM WR_CAS (w/ and w/out auto-pr…
113 …"PublicDescription": "Counts the total number or DRAM Write CAS commands issued on this channel wh…
|
| /Linux-v5.15/include/linux/mlx4/ |
| D | cmd.h | 42 /* initialization and general commands */
81 /* TPT commands */
89 /* EQ commands */
95 /* CQ commands */
101 /* SRQ commands */
107 /* QP/EE commands */
123 /* special QP and management commands */
128 /* multicast commands */
133 /* miscellaneous commands */
140 /* Ethernet specific commands */
[all …]
|
| /Linux-v5.15/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
|
| /Linux-v5.15/kernel/debug/kdb/ |
| D | kdb_cmds | 1 # Initial commands for kdb, alter to suit your needs.
2 # These commands are executed in kdb_init() context, no SMP, no
3 # processes. Commands that require process data (including stack or
4 # registers) are not reliable this early. set and bp commands should
5 # be safe. Global breakpoint commands affect each cpu as it is booted.
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | uncore-memory.json | 53 "BriefDescription": "DRAM Precharge commands. : Precharge due to read",
63 "BriefDescription": "DRAM Precharge commands. : Precharge due to write",
73 "BriefDescription": "All DRAM read CAS commands issued (including underfills)",
83 "BriefDescription": "All DRAM write CAS commands issued",
93 "BriefDescription": "All DRAM CAS commands issued",
173 "BriefDescription": "DRAM Precharge commands. : Precharge due to page table",
246 "BriefDescription": "DRAM Precharge commands",
284 "BriefDescription": "PMM Commands : All",
294 "BriefDescription": "PMM Commands : Reads - RPQ",
304 "BriefDescription": "PMM Commands : Writes",
[all …]
|
| /Linux-v5.15/drivers/net/ethernet/broadcom/bnx2x/ |
| D | bnx2x_sp.h | 31 /* Wait until all pending commands complete */
40 * commands. If not set a new command will be added to the
41 * pending commands list.
101 /************************* VLAN-MAC commands related parameters ***************/
123 /* VLAN_MAC commands */
193 /* Commands pending for an execution. */
196 /* Commands pending for an completion. */
201 /* Maximum length of commands' list for one execution */
208 * Called before commands execution for commands that are really
216 * Called before removing pending commands, cleaning allocated
[all …]
|
| /Linux-v5.15/tools/testing/selftests/tc-testing/ |
| D | README | 30 teardown commands - which includes not being able to run a test simply
52 commands being tested must be run as root. The code that enforces
57 requirement for that test. nsPlugin executes all commands within a
86 The setup and teardown stages can run zero or more commands. The setup
89 can be run next. These two stages require any commands run to return
97 Each of the commands in any stage will run in a shell instance.
105 the tests to be run. These values are used in the tc commands that will be
111 The NAMES values are used to substitute into the commands in the test cases.
128 -v, --verbose Show the commands that are being run
161 options for nsPlugin (run commands in net namespace)
[all …]
|
| /Linux-v5.15/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::
|
| /Linux-v5.15/drivers/scsi/megaraid/ |
| D | mega_common.h | 57 * This is our central data structure to issue commands the each driver.
103 * @outstanding_cmds : number of commands pending in the driver
107 * @pend_list : pending commands list
108 * @pend_list_lock : exclusion lock for pending commands list
109 * @completed_list : list of completed commands
110 * @completed_list_lock : exclusion lock for list of completed commands
120 * @ibuf : buffer to issue internal commands
123 * @uscb_pool : pool of SCBs for user commands
125 * @max_cmds : max outstanding commands
132 * @cmd_per_lun : max outstanding commands per LUN
[all …]
|
| /Linux-v5.15/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 …]
|
| /Linux-v5.15/drivers/net/ethernet/intel/iavf/ |
| D | iavf_adminq_cmd.h | 7 /* This header file defines the iavf Admin Queue commands and is shared between
107 /* aq commands */
120 /* Proxy commands */
131 /* WoL commands */
135 /* internal switch commands */
182 /* DCB commands */
210 /* phy commands*/
228 /* NVM commands */
237 /* virtualization commands */
251 /* LLDP commands */
[all …]
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | libata.rst | 143 Allow low-level driver to filter ATA PACKET commands, returning a status
201 typically raid controllers that use ATA commands but do not actually do
407 Origins of commands
417 libata commands can originate from two sources - libata itself and SCSI
418 midlayer. libata internal commands are used for initialization and error
419 handling. All normal blk requests and commands for SCSI emulation are
420 passed as SCSI commands through queuecommand callback of SCSI host
423 How commands are issued
426 Internal commands
429 mechanism when qc is not available, internal commands are currently
[all …]
|
| /Linux-v5.15/tools/bpf/bpftool/Documentation/ |
| D | bpftool.rst | 24 *MAP-COMMANDS* :=
28 *PROG-COMMANDS* := { **show** | **list** | **dump jited** | **dump xlated** | **pin** |
31 *CGROUP-COMMANDS* := { **show** | **list** | **attach** | **detach** | **help** }
33 *PERF-COMMANDS* := { **show** | **list** | **help** }
35 *NET-COMMANDS* := { **show** | **list** | **help** }
37 *FEATURE-COMMANDS* := { **probe** | **help** }
|
