| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/drivers/media/pci/cx23885/ |
| D | cx23885-ir.c | 38 unsigned long *notifications = &dev->ir_rx_notifications; in cx23885_ir_rx_work_handler() local
40 if (test_and_clear_bit(CX23885_IR_RX_SW_FIFO_OVERRUN, notifications)) in cx23885_ir_rx_work_handler()
42 if (test_and_clear_bit(CX23885_IR_RX_HW_FIFO_OVERRUN, notifications)) in cx23885_ir_rx_work_handler()
44 if (test_and_clear_bit(CX23885_IR_RX_END_OF_RX_DETECTED, notifications)) in cx23885_ir_rx_work_handler()
46 if (test_and_clear_bit(CX23885_IR_RX_FIFO_SERVICE_REQ, notifications)) in cx23885_ir_rx_work_handler()
61 unsigned long *notifications = &dev->ir_tx_notifications; in cx23885_ir_tx_work_handler() local
63 if (test_and_clear_bit(CX23885_IR_TX_FIFO_SERVICE_REQ, notifications)) in cx23885_ir_tx_work_handler()
75 unsigned long *notifications = &dev->ir_rx_notifications; in cx23885_ir_rx_v4l2_dev_notify() local
78 set_bit(CX23885_IR_RX_FIFO_SERVICE_REQ, notifications); in cx23885_ir_rx_v4l2_dev_notify()
80 set_bit(CX23885_IR_RX_END_OF_RX_DETECTED, notifications); in cx23885_ir_rx_v4l2_dev_notify()
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | cpu_pm.h | 32 * All cpu_pm notifications must be called with interrupts disabled.
34 * The notifications are split into two classes: CPU notifications and CPU
35 * cluster notifications.
37 * CPU notifications apply to a single CPU and must be called on the affected
40 * CPU cluster notifications apply to all CPUs in a single power domain. They
|
| /kernel/linux/linux-4.19/Documentation/thermal/ |
| D | x86_pkg_temperature_thermal | 39 Any value other than 0 in these trip points, can trigger thermal notifications.
40 Setting 0, stops sending thermal notifications.
42 Thermal notifications: To get kobject-uevent notifications, set the thermal zone
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | dnotify.txt | 9 on a directory using a fcntl(2) call and the notifications themselves
34 (SIGRTMIN + <n>) so that the notifications may be queued. This is
50 name "a/x" should be notified to a program expecting notifications on
51 directory "a", but will not be notified to one expecting notifications on
54 Also, files that are unlinked, will still cause notifications in the
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/drivers/uwb/ |
| D | neh.c | 24 * card delivers a stream of notifications and events to the
27 * notifications and events and then deliver those.
30 * associates them to the command. Notifications are that,
31 * notifications, they come out of the blue and have a context ID of
62 * - Most notifications/events are small (less thank .5k), copying
65 * - Notifications/events are ALWAYS smaller than PAGE_SIZE
67 * - Notifications/events always come in a single piece (ie: a buffer
68 * will always contain entire notifications/events).
77 * - Most notifications/events are fixed size; only a few are variable
81 * buffer, as they know the size. Listeners to notifications don't,
[all …]
|
| /kernel/linux/linux-4.19/Documentation/acpi/ |
| D | acpi-lid.txt | 15 For most platforms, both the _LID method and the lid notifications are
33 2. Restrictions of the lid state change notifications
86 ensure that the reliable "closed" notifications can always be delievered
89 notifications can be delivered to the userspace when the lid is actually
90 opens given that some AML tables do not send "opened" notifications
|
| /kernel/linux/linux-4.19/drivers/usb/wusbcore/ |
| D | wa-nep.c | 13 * WA notifications are limited in size; most of them are three or
26 * workqueue (so notifications are serialized) and copy the
45 /* Structure for queueing notifications to the workqueue */
54 * Process incoming notifications from the WA's Notification EndPoint
62 * All notifications follow the same format; they need to start with a
64 * them. We just break the buffer in individual notifications (the
155 * Deliver incoming WA notifications to the wusbwa workqueue
178 dev_err(dev, "Too many notifications queued, " in wa_nep_queue()
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/ |
| 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::
|
| /kernel/linux/linux-4.19/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 174 and sends the replies and notifications back to the API
175 [/uwb_rc_neh_grok()/]. Notifications are handled to the UWB daemon, that
223 control interface will send beacon notifications on its
224 notification/event endpoint (NEEP). The beacon notifications are part of
246 processing of incoming *DRP Availability Change* notifications. This
279 three endpoints (Notifications, Data Transfer In and Data Transfer
290 WUSB IEs (host to device commands/notifications) and Device
291 Notifications (device initiated to host). Each host defines a
423 Handle/file descriptor for receiving notifications or events. The WA
424 code requires you to get one of this to listen for notifications or
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/s390/ |
| D | qeth.txt | 24 notifications enabled, a udev event with ACTION=CHANGE is emitted.
30 notifications are started afresh, a new host or VLAN is registered or
32 notifications are aborted.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 66 events, except page fault notifications, may be generated.
79 If the userland desires to receive notifications for events other than
133 Write Protect Notifications
232 the same read(2) protocol as for the page fault notifications. The
244 enable notifications about mremap() calls. When the
251 enable notifications about madvise(MADV_REMOVE) and
257 enable notifications about memory unmapping. The manager will
|
| /kernel/linux/linux-5.10/include/media/i2c/ |
| D | bt819.h | 3 bt819.h - bt819 notifications
14 /* v4l2_device notifications. */
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 66 events, except page fault notifications, may be generated.
79 If the userland desires to receive notifications for events other than
180 the same read(2) protocol as for the page fault notifications. The
192 enable notifications about mremap() calls. When the
199 enable notifications about madvise(MADV_REMOVE) and
205 enable notifications about memory unmapping. The manager will
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/include/uapi/linux/ |
| D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
74 * datapath. Always present in notifications.
76 * datapath. Always present in notifications.
137 /* Kernel-to-user notifications. */
147 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
152 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
526 * key. Always present in notifications. Required for all requests (except
530 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
535 * flow. Present in notifications if the stats would be nonzero. Ignored in
538 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
74 * datapath. Always present in notifications.
76 * datapath. Always present in notifications.
141 /* Kernel-to-user notifications. */
151 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
156 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
533 * key. Always present in notifications. Required for all requests (except
537 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
542 * flow. Present in notifications if the stats would be nonzero. Ignored in
545 * 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 */
|