| /Linux-v6.1/drivers/media/pci/cx23885/ |
| D | cx23885-ir.c | 29 unsigned long *notifications = &dev->ir_rx_notifications; in cx23885_ir_rx_work_handler() local
31 if (test_and_clear_bit(CX23885_IR_RX_SW_FIFO_OVERRUN, notifications)) in cx23885_ir_rx_work_handler()
33 if (test_and_clear_bit(CX23885_IR_RX_HW_FIFO_OVERRUN, notifications)) in cx23885_ir_rx_work_handler()
35 if (test_and_clear_bit(CX23885_IR_RX_END_OF_RX_DETECTED, notifications)) in cx23885_ir_rx_work_handler()
37 if (test_and_clear_bit(CX23885_IR_RX_FIFO_SERVICE_REQ, notifications)) in cx23885_ir_rx_work_handler()
52 unsigned long *notifications = &dev->ir_tx_notifications; in cx23885_ir_tx_work_handler() local
54 if (test_and_clear_bit(CX23885_IR_TX_FIFO_SERVICE_REQ, notifications)) in cx23885_ir_tx_work_handler()
66 unsigned long *notifications = &dev->ir_rx_notifications; in cx23885_ir_rx_v4l2_dev_notify() local
69 set_bit(CX23885_IR_RX_FIFO_SERVICE_REQ, notifications); in cx23885_ir_rx_v4l2_dev_notify()
71 set_bit(CX23885_IR_RX_END_OF_RX_DETECTED, notifications); in cx23885_ir_rx_v4l2_dev_notify()
[all …]
|
| /Linux-v6.1/tools/testing/selftests/drivers/net/netdevsim/ |
| D | fib_notifications.sh | 66 check_err $? "$expected_num_lines notifications were expected but $lines were received"
74 check_err $? "Wrong RTM_F_TRAP flags in notifications"
77 check_err $? "Wrong RTM_F_OFFLOAD_FAILED flags in notifications"
119 # Make sure two notifications will be emitted for the programmed route.
124 # notify=2 means emit notifications only for failed route installation,
218 # Make sure two notifications will be emitted for the new route.
223 # notify=2 means emit notifications only for failed route installation,
253 # Make sure two notifications will be emitted for the new route.
259 # notify=2 means emit notifications only for failed route installation,
260 # make sure two notifications will be emitted for the new route.
[all …]
|
| /Linux-v6.1/include/linux/ |
| D | cpu_pm.h | 23 * All cpu_pm notifications must be called with interrupts disabled.
25 * The notifications are split into two classes: CPU notifications and CPU
26 * cluster notifications.
28 * CPU notifications apply to a single CPU and must be called on the affected
31 * CPU cluster notifications apply to all CPUs in a single power domain. They
|
| D | virtio_pci_modern.h | 21 /* Base of vq notifications (non-legacy mode). */
23 /* Physical base of vq notifications */
32 /* Capability for when we need to map notifications per-vq. */
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | x86_pkg_temperature_thermal.rst | 46 Any value other than 0 in these trip points, can trigger thermal notifications.
47 Setting 0, stops sending thermal notifications.
49 Thermal notifications:
50 To get kobject-uevent notifications, set the thermal zone
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | dnotify.rst | 12 on a directory using a fcntl(2) call and the notifications themselves
39 (SIGRTMIN + <n>) so that the notifications may be queued. This is
55 name "a/x" should be notified to a program expecting notifications on
56 directory "a", but will not be notified to one expecting notifications on
59 Also, files that are unlinked, will still cause notifications in the
|
| /Linux-v6.1/Documentation/networking/ |
| D | msg_zerocopy.rst | 99 Notifications section in Interface
103 previously passed buffer. It queues completion notifications on the
139 efficient to not wait for notifications, but read without blocking
142 Notifications can be processed out of order with other operations on
144 other operations until the error is read. Zerocopy notifications have
153 a single value, but a range. It coalesces consecutive notifications
165 Ordered delivery is the common case, but not guaranteed. Notifications argument
|
| /Linux-v6.1/Documentation/core-api/ |
| D | watch_queue.rst | 9 * Key/keyring notifications
12 The notifications buffers can be enabled by:
47 notifications can be generated whilst spinlocks are held and also protects the
98 notifications. A list may be attached to an object (say a key or a superblock)
168 The ``id`` field is the source's ID. Notifications that are posted with a
235 Notifications of this type indicate changes to keys and keyrings, including
299 It can then be set to receive keyring change notifications::
303 The notifications can then be consumed by something like the following::
|
| /Linux-v6.1/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 20 For most platforms, both the _LID method and the lid notifications are
39 Restrictions of the lid state change notifications
103 ensure that the reliable "closed" notifications can always be delivered
106 notifications can be delivered to the userspace when the lid is actually
107 opens given that some AML tables do not send "opened" notifications
|
| /Linux-v6.1/Documentation/s390/ |
| D | qeth.rst | 31 notifications enabled, a udev event with ACTION=CHANGE is emitted.
38 notifications are started afresh, a new host or VLAN is registered or
40 notifications are aborted.
|
| /Linux-v6.1/Documentation/bpf/ |
| D | ringbuf.rst | 80 - epoll notifications for new incoming data;
136 notifications about new data availability in ring buffer. Together with
139 efficient batched notifications. Default self-balancing strategy, though,
195 a self-pacing notifications of new data being availability.
204 notifications, commit/discard/output helpers accept ``BPF_RB_NO_WAKEUP`` and
205 ``BPF_RB_FORCE_WAKEUP`` flags, which give full control over notifications of
|
| /Linux-v6.1/Documentation/userspace-api/netlink/ |
| D | intro.rst | 141 - getting asynchronous notifications (``multicast``).
147 Asynchronous notifications are sent by the kernel and received by
159 matching responses to requests. Asynchronous notifications will have
434 Multicast notifications
437 One of the strengths of Netlink is the ability to send event notifications
443 notifications about registered families. When a new family is added the
444 sockets subscribed to the notifications will get the following message::
488 To receive notifications the user socket must subscribe to the relevant
506 The socket will now receive notifications.
508 It is recommended to use separate sockets for receiving notifications
[all …]
|
| /Linux-v6.1/include/media/i2c/ |
| D | bt819.h | 3 bt819.h - bt819 notifications
14 /* v4l2_device notifications. */
|
| /Linux-v6.1/Documentation/staging/ |
| D | tee.rst | 187 OP-TEE notifications
190 There are two kinds of notifications that secure world can use to make
193 1. Synchronous notifications delivered with ``OPTEE_RPC_CMD_NOTIFICATION``
195 2. Asynchronous notifications delivered with a combination of a non-secure
199 Synchronous notifications are limited by depending on RPC for delivery,
201 ``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure
208 multiple notifications.
|
| /Linux-v6.1/include/xen/interface/hvm/ |
| D | params.h | 14 * How should CPU0 event-channel notifications be delivered?
16 * If val == 0 then CPU0 event-channel notifications are not delivered.
23 * and disables all notifications.
|
| /Linux-v6.1/drivers/virtio/ |
| D | Kconfig | 40 Enable this to harden the device notifications and suppress
41 those that happen at a time where notifications are illegal.
45 notifications is enforced; depending on the subset of
|
| /Linux-v6.1/include/uapi/linux/ |
| D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
76 * datapath. Always present in notifications.
78 * datapath. Always present in notifications.
152 /* Kernel-to-user notifications. */
162 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
167 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
560 * key. Always present in notifications. Required for all requests (except
564 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
569 * flow. Present in notifications if the stats would be nonzero. Ignored in
572 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| D | selinux_netlink.h | 3 * Netlink event notifications for SELinux.
29 #define SELNL_GRP_AVC 0x00000001 /* AVC notifications */
|
| /Linux-v6.1/drivers/rapidio/switches/ |
| D | idt_gen3.c | 171 /* Disable port-write event notifications during initialization */ in idtg3_em_init()
175 /* Configure Port-Write notifications for hot-swap events */ in idtg3_em_init()
189 /* Enable event notifications */ in idtg3_em_init()
204 /* Enable sending port-write event notifications */ in idtg3_em_init()
329 /* Disable sending port-write event notifications if PW destID in idtg3_shutdown()
|
| /Linux-v6.1/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 18 the locking involved. It outlines the notifications involved as well.
44 notifications
68 | While it is at it, notifications |
105 * send PM_POST_SUSPEND notifications
141 | While it is at it, notifications
|
| /Linux-v6.1/mm/ |
| D | vmpressure.c | 30 * delay the notifications.
349 * vmpressure_register_event() - Bind vmpressure notifications to an eventfd
350 * @memcg: memcg that is interested in vmpressure notifications
351 * @eventfd: eventfd context to link notifications with
355 * infrastructure, so that the notifications will be delivered to the
422 * the vmpressure notifications, and then frees internal resources
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 101 events, except page fault notifications, may be generated:
194 Write Protect Notifications
293 the same read(2) protocol as for the page fault notifications. The
305 enable notifications about mremap() calls. When the
312 enable notifications about madvise(MADV_REMOVE) and
318 enable notifications about memory unmapping. The manager will
|
| /Linux-v6.1/drivers/dma/fsl-dpaa2-qdma/ |
| D | dpdmai.h | 102 * and does not generate FQDAN notifications; user is expected to dequeue
105 * notifications to the specified DPIO; user is expected to dequeue
108 * FQDAN notifications, but is connected to the specified DPCON object;
|
| /Linux-v6.1/drivers/gpu/drm/radeon/ |
| D | radeon_acpi.c | 52 u32 notification_mask; /* supported notifications mask */
152 * radeon_atif_parse_notification - parse supported notifications
154 * @n: supported notifications struct
155 * @mask: supported notifications mask from ATIF
157 * Use the supported notifications mask from ATIF function
158 * ATIF_FUNCTION_VERIFY_INTERFACE to determine what notifications
236 radeon_atif_parse_notification(&atif->notifications, output.notification_mask); in radeon_atif_verify_interface()
734 if (atif->notifications.brightness_change) { in radeon_acpi_init()
|
| /Linux-v6.1/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | time-event.h | 83 * @TE_V1_NOTIF_NONE: no notifications
93 * Supported Time event notifications configuration.
167 /* notifications (event start/stop, fragment start/stop) */
246 * struct iwl_time_event_notif - notifications of time event start/stop
408 * Note that any session protection will always get two notifications: start
|
