Home
last modified time | relevance | path

Searched refs:messages (Results 1 – 25 of 480) sorted by relevance

12345678910>>...20

/linux/drivers/media/pci/bt8xx/
A Ddst_ca.c141 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()
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()
187 num_ids = state->messages[in_num_ids_pos]; in ca_get_ca_info()
198 …dprintk(verbose, DST_CA_INFO, 0, " 0x%02x%02x", state->messages[srcPtr + 0], state->messages[srcPt… in ca_get_ca_info()
200 state->messages[dstPtr + 0] = state->messages[srcPtr + 0]; in ca_get_ca_info()
201 state->messages[dstPtr + 1] = state->messages[srcPtr + 1]; in ca_get_ca_info()
[all …]
/linux/net/mac80211/
A DKconfig88 bool "Trace all mac80211 debug messages"
93 collect all debugging messages, independent of
138 debugging messages for the managed-mode MLME. It
140 of the messages are remotely triggerable.
149 debugging messages for station addition/removal.
161 of the messages are remotely triggerable.
195 messages are remotely triggerable.
208 messages are remotely triggerable.
221 messages are remotely triggerable.
234 messages are remotely triggerable.
[all …]
/linux/tools/testing/selftests/ipc/
A Dmsgque.c32 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/sound/usb/line6/
A Ddriver.c541 line6->messages.active = 1; in line6_hwdep_open()
552 line6->messages.active = 0; in line6_hwdep_release()
572 if (line6->messages.nonblock) in line6_hwdep_read()
576 line6->messages.wait_queue, in line6_hwdep_read()
577 kfifo_len(&line6->messages.fifo) != 0); in line6_hwdep_read()
630 mutex_lock(&line6->messages.read_lock); in line6_hwdep_poll()
648 if (!line6->messages.active) in line6_hwdep_push_message()
653 kfifo_in(&line6->messages.fifo, in line6_hwdep_push_message()
667 line6->messages.active = 0; in line6_hwdep_init()
669 mutex_init(&line6->messages.read_lock); in line6_hwdep_init()
[all …]
/linux/arch/sh/kernel/cpu/sh2/
A Dsmp-j2.c25 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/
A Dkcm.rst9 can efficiently send and receive application protocol messages over TCP using
48 (Psock) and complete messages are steered to a KCM socket.
63 can be used to send and receive messages from the KCM socket.
193 When receive is disabled, any pending messages in the socket's
196 work on a request and won't be able to service new messages for a
225 messages. The kernel provides necessary assurances that messages are sent
256 messages on a KCM socket.
258 1) Send multiple messages in a single sendmmsg.
259 2) Send a group of messages each with a sendmsg call, where all messages
261 3) Create "super message" composed of multiple messages and send this
[all …]
A Dnetif-msg.rst23 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.
A Dtls.rst123 Send TLS control messages
126 Other than application data, TLS has control messages such as alert
127 messages (record type 21) and handshake messages (record type 22), etc.
128 These messages can be sent over the socket by providing the TLS record type
164 Receiving TLS control messages
167 TLS control messages are passed in the userspace buffer, with message
169 returned if a control message is received. Data messages may be
215 messages are not supported.
A Dipvs-sysctl.rst79 - 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
180 It controls sending icmp error messages (ICMP_DEST_UNREACH)
219 new sync message. It can be used to avoid sync messages for the
231 to protect against loss of sync messages. The range of the
236 Hard limit for queued sync messages that are not sent yet. It
238 number of messages. It will protect us from allocating large
291 synchronisation messages.
[all …]
/linux/Documentation/userspace-api/media/cec/
A Dcec-ioc-g-mode.rst42 used to initiate messages, i.e. it commands other CEC devices. The
43 follower is the filehandle that receives messages sent to the CEC
62 case, the CEC framework will pass on most core messages without
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
138 receive CEC messages for processing. If someone else is already
148 receive CEC messages for processing. In addition it will put the
150 to handle most core messages instead of relying on the CEC
177 In monitor mode all messages this CEC
178 device transmits and all messages it receives (both broadcast
[all …]
/linux/Documentation/firmware-guide/acpi/
A Ddebug.rst14 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/
A Ddev-kmsg8 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
A Dsysfs-bus-pci-devices-aer_stats97 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/fs/ntfs/
A DKconfig36 performed by the driver as well as additional debugging messages to
37 be written to the system log. Note that debugging messages are
41 you can enable debugging messages by doing (as root):
43 Replacing the "1" with "0" would disable debug messages.
45 If you leave debugging messages disabled, this results in little
46 overhead, but enabling debug messages results in very significant
50 debugging messages while the misbehaviour was occurring.
/linux/arch/arm/
A DKconfig.debug88 bool "Verbose user fault messages"
123 bool "Kernel low-level debugging messages via Alpine UART0"
233 bool "Kernel low-level debugging messages via BCM KONA UART"
265 messages to appear over the UART, select this option.
268 bool "Kernel low-level debugging messages via UART1"
275 bool "Kernel low-level debugging messages via UART2"
321 bool "Kernel low-level debugging messages via Digicolor UA0"
328 bool "Kernel low-level debugging messages via ep93xx UART"
800 bool "Kernel low-level debugging messages via QCOM UARTDM"
1132 bool "Kernel low-level debugging messages via sun9i UART0"
[all …]
/linux/drivers/pnp/
A DKconfig26 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/
A DKconfig5 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/drivers/atm/
A DKconfig222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
226 messages is controlled by a bitmap. This may be specified as a
257 bool "Enable debugging messages"
260 Somewhat useful debugging messages are available. The choice of
261 messages is controlled by a bitmap. This may be specified as a
281 bool "Enable debugging messages"
284 Somewhat useful debugging messages are available. The choice of
314 bool "Enable debugging messages"
318 messages is controlled by a bitmap. This may be specified as a
[all …]
/linux/Documentation/misc-devices/
A Dibmvmc.rst50 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/
A DKconfig56 messages to trace hosts over STM devices.
58 If you want to send kernel console messages over STM devices,
65 heartbeat messages to trace hosts over STM devices. It is
69 If you want to send heartbeat messages over STM devices,
80 If you want to send kernel Ftrace messages over STM devices,
/linux/Documentation/admin-guide/blockdev/
A Dfloppy.rst49 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/hwmon/
A Dsubmitting-patches.rst20 errors, no warnings, and few if any check messages. If there are any
21 messages, please be prepared to explain.
27 * If your patch generates checkpatch errors, warnings, or check messages,
88 * Limit the number of kernel log messages. In general, your driver should not
91 that kernel error log messages not only fill up the kernel log, but also are
99 * If the driver has a detect function, make sure it is silent. Debug messages
100 and messages printed after a successful detection are acceptable, but it
101 must not print messages such as "Chip XXX not found/supported".
104 address if a chip is detected on that address. Unnecessary messages will just
/linux/sound/firewire/motu/
A Damdtp-motu-trace.h57 __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/driver-api/nfc/
A Dnfc-pn544.rst26 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/net/sctp/
A DKconfig26 -- 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

Completed in 48 milliseconds

12345678910>>...20