/linux/drivers/media/pci/bt8xx/ |
H A D | dst_ca.c | 134 if ((dst_put_ci(state, command, sizeof(command), state->messages, GET_REPLY)) < 0) { in ca_get_app_info() 141 state->messages[7], (state->messages[8] << 8) | state->messages[9], in ca_get_app_info() 142 (state->messages[10] << 8) | state->messages[11], __func__, (char *)(&state->messages[12])); in ca_get_app_info() 146 length = state->messages[5]; in ca_get_app_info() 154 put_command_and_length(&state->messages[0], CA_APP_INFO, length); in ca_get_app_info() 157 memmove(&state->messages[4], &state->messages[7], 5); in ca_get_app_info() 160 state->messages[9] = str_length; in ca_get_app_info() 161 memmove(&state->messages[10], &state->messages[12], str_length); in ca_get_app_info() 173 if ((dst_put_ci(state, slot_command, sizeof (slot_command), state->messages, GET_REPLY)) < 0) { in ca_get_ca_info() 181 for (i = 0; i < state->messages[0] + 1; i++) { in ca_get_ca_info() [all …]
|
/linux/tools/testing/selftests/ipc/ |
H A D | msgque.c | 32 struct msg1 *messages; member 67 if (msgsnd(msgque->msq_id, &msgque->messages[i].mtype, in restore_queue() 68 msgque->messages[i].msize, IPC_NOWAIT) != 0) { in restore_queue() 97 if (ret != msgque->messages[cnt].msize) { in check_and_destroy_queue() 99 msgque->messages[cnt].msize); in check_and_destroy_queue() 103 if (message.mtype != msgque->messages[cnt].mtype) { in check_and_destroy_queue() 108 if (memcmp(message.mtext, msgque->messages[cnt].mtext, ret)) { in check_and_destroy_queue() 151 msgque->messages = malloc(sizeof(struct msg1) * ds.msg_qnum); in dump_queue() 152 if (msgque->messages == NULL) { in dump_queue() 162 ret = msgrcv(msgque->msq_id, &msgque->messages[i].mtype, in dump_queue() [all …]
|
/linux/net/mac80211/ |
H A D | Kconfig | 98 bool "Trace all mac80211 debug messages" 103 collect all debugging messages, independent of 106 The overhead in this option is that all the messages 137 many debugging messages. It should not be selected 138 on production systems as some of the messages are 148 debugging messages for the managed-mode MLME. It 150 of the messages are remotely triggerable. 159 debugging messages for station addition/removal. 171 of the messages are remotely triggerable. 180 very verbose OCB debugging messages. It should not [all …]
|
/linux/sound/usb/line6/ |
H A D | driver.c | 547 line6->messages.active = 1; in line6_hwdep_open() 548 line6->messages.nonblock = file->f_flags & O_NONBLOCK ? 1 : 0; in line6_hwdep_open() 558 line6->messages.active = 0; in line6_hwdep_release() 572 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read() 575 while (kfifo_len(&line6->messages.fifo) == 0) { in line6_hwdep_read() 576 mutex_unlock(&line6->messages.read_lock); in line6_hwdep_read() 578 if (line6->messages.nonblock) in line6_hwdep_read() 582 line6->messages.wait_queue, in line6_hwdep_read() 583 kfifo_len(&line6->messages.fifo) != 0); in line6_hwdep_read() 587 if (mutex_lock_interruptible(&line6->messages.read_lock)) in line6_hwdep_read() [all …]
|
/linux/arch/sh/kernel/cpu/sh2/ |
H A D | smp-j2.c | 25 unsigned messages, i; in j2_ipi_interrupt_handler() local 27 do messages = *pmsg; in j2_ipi_interrupt_handler() 28 while (cmpxchg(pmsg, messages, 0) != messages); in j2_ipi_interrupt_handler() 30 if (!messages) return IRQ_NONE; in j2_ipi_interrupt_handler() 33 if (messages & (1U<<i)) in j2_ipi_interrupt_handler()
|
/linux/Documentation/networking/ |
H A D | netif-msg.rst | 23 to shed the more verbose level messages as they matured. 25 - 0 Minimal messages, only essential information on fatal errors. 26 - 1 Standard messages, initialization status. No run-time messages 27 - 2 Special media selection messages, generally timer-driver. 28 - 3 Interface starts and stops, including normal status messages 29 - 4 Tx and Rx frame error messages, and abnormal driver operation 46 - More selective control over the type of messages emitted.
|
H A D | kcm.rst | 9 can efficiently send and receive application protocol messages over TCP using 45 The multiplexor provides the message steering. In the transmit path, messages 47 Similarly, in the receive path, messages are constructed on each TCP socket 48 (Psock) and complete messages are steered to a KCM socket. 55 messages on receive as well as other connection specific information for KCM. 63 can be used to send and receive messages from the KCM socket. 74 format that typically includes a header which frames the messages. The length 102 socket. The BPF program may also enforce a maximum messages size and report an 105 A timeout may be set for assembling messages on a receive socket. The timeout 193 When receive is disabled, any pending messages in the socket's [all …]
|
H A D | ipvs-sysctl.rst | 79 - 0 - transmission error messages (default) 80 - 1 - non-fatal error messages 95 Higher debugging levels include the messages for lower debugging 97 messages. Thus, logging becomes more and more verbose the higher 200 It controls sending icmp error messages (ICMP_DEST_UNREACH) 239 new sync message. It can be used to avoid sync messages for the 251 to protect against loss of sync messages. The range of the 256 Hard limit for queued sync messages that are not sent yet. It 258 number of messages. It will protect us from allocating large 311 synchronisation messages. [all …]
|
/linux/Documentation/userspace-api/media/cec/ |
H A D | cec-ioc-g-mode.rst | 42 used to initiate messages, i.e. it commands other CEC devices. The 43 follower is the filehandle that receives messages sent to the CEC 60 The CEC framework will process core messages unless requested otherwise 62 case, the CEC framework will pass on most core messages without 63 processing them and the follower will have to implement those messages. 64 There are some messages that the core will always process, regardless of 88 - This is not an initiator, i.e. it cannot transmit CEC messages or 95 it can transmit CEC messages and make changes to the CEC adapter, 102 only one that can transmit CEC messages and make changes to the 129 - This is a follower and it will receive CEC messages unless there [all …]
|
H A D | cec-ioc-adap-g-caps.rst | 96 - Userspace can transmit CEC messages by calling 99 messages is a prerequisite of becoming a follower. If this 101 transmits and process all CEC messages it receives. 117 - The CEC hardware can monitor all messages, not just directed and 118 broadcast messages.
|
/linux/Documentation/firmware-guide/acpi/ |
H A D | debug.rst | 14 config option is not set, the debug messages are not even built into the kernel. 19 When CONFIG_ACPI_DEBUG=y, you can select the component and level of messages 23 the debug messages. 58 The "debug_level" is a mask that selects different types of messages, e.g., 59 those related to initialization, method execution, informational messages, etc. 122 Enable all ACPI hardware-related messages:: 126 Enable all ACPI_DB_INFO messages after boot::
|
/linux/Documentation/ABI/testing/ |
H A D | dev-kmsg | 8 Injecting messages: 20 is not possible to inject messages from userspace with the 22 the messages can always be reliably determined. 39 there are never partial messages received by read(). 41 In case messages get overwritten in the circular buffer while 48 messages, in case the buffer gets overwritten. And they allow 64 or write only whole variable length messages (records) that are 113 interleaved with unrelated messages, but merging the lines in 115 similar logic is used internally when messages are printed to
|
H A D | sysfs-bus-pci-devices-aer_stats | 97 collectors) that are AER capable. These indicate the number of error messages as 99 (internally) the ERR_* messages for errors seen by the internal rootport PCI 101 messages on the PCI hierarchy originating at that root port. 107 Description: Total number of ERR_COR messages reported to rootport. 113 Description: Total number of ERR_FATAL messages reported to rootport. 119 Description: Total number of ERR_NONFATAL messages reported to rootport.
|
/linux/drivers/pnp/ |
H A D | Kconfig | 26 bool "PNP debugging messages" 30 messages if needed. The messages can be enabled at boot-time with 34 the messages to even be built into the kernel.
|
/linux/net/dccp/ccids/ |
H A D | Kconfig | 5 bool "CCID-2 debugging messages" 7 Enable CCID-2 specific debugging messages. 40 bool "CCID-3 debugging messages" 43 Enable CCID-3 specific debugging messages.
|
/linux/tools/crypto/ccp/ |
H A D | dbc_cli.py | 20 messages = { variable 51 parser.add_argument("--message", choices=messages.keys(), help="Message index") 113 param, signature = process_param(d, messages[args.message], sig) 126 param, signature = process_param(d, messages[args.message], sig, data)
|
/linux/Documentation/misc-devices/ |
H A D | ibmvmc.rst | 50 The set of HMC to hypervisor messages supported by the management 77 sending/receiving any of the protocol messages. 79 This driver also utilizes Transport Event CRQs. CRQ messages are sent 82 Two new classes of CRQ messages are introduced for the VMC device. VMC 83 Administrative messages are used for each partition using the VMC to 84 communicate capabilities to their partner. HMC Interface messages are used 85 for the actual flow of HMC messages between the management partition and 86 the hypervisor. As most HMC messages far exceed the size of a CRQ buffer, 154 hypervisor receives this information, it sends Add Buffer messages to the 178 exchange HMC messages via the Signal VMC message and RDMA operations. When [all …]
|
/linux/drivers/hwtracing/stm/ |
H A D | Kconfig | 55 messages to trace hosts over STM devices. 57 If you want to send kernel console messages over STM devices, 64 heartbeat messages to trace hosts over STM devices. It is 68 If you want to send heartbeat messages over STM devices, 79 If you want to send kernel Ftrace messages over STM devices,
|
/linux/Documentation/admin-guide/blockdev/ |
H A D | floppy.rst | 49 modprobe floppy floppy="omnibook messages" 54 options floppy floppy="omnibook messages" 94 if you frequently get "Unable to allocate DMA memory" messages. 114 master arbitration error" messages from your Ethernet card (or 129 To tune the fifo threshold, switch on over/underrun messages 130 using 'floppycontrol --messages'. Then access a floppy 132 messages, then the fifo threshold is too low. Try with a 137 that you need to do 'floppycontrol --messages' every time you 187 Print debugging messages. 189 floppy=messages [all …]
|
/linux/Documentation/driver-api/nfc/ |
H A D | nfc-pn544.rst | 26 HCI messages consist of an eight bit header and the message body. The 28 33. In HCI mode sent messages are tested for a correct 29 checksum. Firmware update messages have the length in the second (MSB)
|
/linux/sound/firewire/motu/ |
H A D | amdtp-motu-trace.h | 57 __dynamic_array(u64, messages, data_blocks) 68 copy_message(__get_dynamic_array(messages), buffer, data_blocks, s->data_block_quadlets); 75 __print_array(__get_dynamic_array(messages), __entry->data_blocks, 8)
|
/linux/Documentation/hwmon/ |
H A D | submitting-patches.rst | 19 errors, no warnings, and few if any check messages. If there are any 20 messages, please be prepared to explain. 26 * If your patch generates checkpatch errors, warnings, or check messages, 87 * Limit the number of kernel log messages. In general, your driver should not 90 that kernel error log messages not only fill up the kernel log, but also are 98 * If the driver has a detect function, make sure it is silent. Debug messages 99 and messages printed after a successful detection are acceptable, but it 100 must not print messages such as "Chip XXX not found/supported". 103 address if a chip is detected on that address. Unnecessary messages will just
|
/linux/net/sctp/ |
H A D | Kconfig | 26 -- sequenced delivery of user messages within multiple streams, 28 messages, 29 -- optional bundling of multiple user messages into a single SCTP 35 module will be called sctp. Debug messages are handled by the
|
/linux/Documentation/core-api/ |
H A D | printk-basics.rst | 8 standard tool we have for printing messages and usually the most basic way of 12 - printk() messages can specify a log level. 19 All printk() messages are printed to the kernel log buffer, which is a ring 73 ``/proc/sys/kernel/printk``. For example, to print all messages to the console:: 81 sets the console_loglevel to print KERN_WARNING (4) or more severe messages to
|
/linux/drivers/crypto/aspeed/ |
H A D | Kconfig | 13 bool "Enable Aspeed crypto debug messages" 16 Print Aspeed crypto debugging messages if you use this 17 option to ask for those messages.
|