| /Linux-v5.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 …]
|
| /Linux-v5.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
|
| D | scmi_protocol.h | 213 * struct scmi_notify_ops - represents notifications' operations provided by
232 * receiving notifications from ANY existent source associated to the
235 * Received notifications are finally delivered to the registered users,
265 * @notify_ops: pointer to set of notifications related operations
276 * @notify_priv: pointer to private data structure specific to notifications
|
| D | mei_cl_bus.h | 32 * Rx buffer pending notifications.
35 * FW notification pending notifications.
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.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::
|
| /Linux-v5.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
|
| /Linux-v5.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.
|
| /Linux-v5.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
|
| /Linux-v5.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
|
| /Linux-v5.10/include/media/i2c/ |
| D | bt819.h | 3 bt819.h - bt819 notifications
14 /* v4l2_device notifications. */
|
| /Linux-v5.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 */
|
| /Linux-v5.10/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-v5.10/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-v5.10/include/xen/interface/hvm/ |
| D | params.h | 32 * How should CPU0 event-channel notifications be delivered?
34 * If val == 0 then CPU0 event-channel notifications are not delivered.
41 * and disables all notifications.
|
| /Linux-v5.10/mm/ |
| D | vmpressure.c | 30 * delay the notifications.
345 * vmpressure_register_event() - Bind vmpressure notifications to an eventfd
346 * @memcg: memcg that is interested in vmpressure notifications
347 * @eventfd: eventfd context to link notifications with
351 * infrastructure, so that the notifications will be delivered to the
418 * the vmpressure notifications, and then frees internal resources
|
| /Linux-v5.10/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-v5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_acpi.c | 64 struct amdgpu_atif_notifications notifications; member
125 * amdgpu_atif_parse_notification - parse supported notifications
127 * @n: supported notifications struct
128 * @mask: supported notifications mask from ATIF
130 * Use the supported notifications mask from ATIF function
131 * ATIF_FUNCTION_VERIFY_INTERFACE to determine what notifications
202 amdgpu_atif_parse_notification(&atif->notifications, output.notification_mask); in amdgpu_atif_verify_interface()
810 if (atif->notifications.brightness_change) { in amdgpu_acpi_init()
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | radeon_acpi.c | 53 u32 notification_mask; /* supported notifications mask */
153 * radeon_atif_parse_notification - parse supported notifications
155 * @n: supported notifications struct
156 * @mask: supported notifications mask from ATIF
158 * Use the supported notifications mask from ATIF function
159 * ATIF_FUNCTION_VERIFY_INTERFACE to determine what notifications
237 radeon_atif_parse_notification(&atif->notifications, output.notification_mask); in radeon_atif_verify_interface()
737 if (atif->notifications.brightness_change) { in radeon_acpi_init()
|
| /Linux-v5.10/drivers/thermal/intel/ |
| D | Kconfig | 20 two trip points which can be set by user to get notifications via thermal
43 be set by user mode programs to get notifications via Linux thermal
|
| /Linux-v5.10/drivers/misc/vmw_vmci/ |
| D | vmci_context.c | 226 * We only deliver notifications of the removal of in ctx_fire_notification()
596 * notifications from/about.
610 pr_devel("Context removed notifications for other VMs not supported (src=0x%x, remote=0x%x)\n", in vmci_ctx_add_notification()
663 * interested in getting notifications from/about.
854 * Retrieves the specified context's pending notifications in the
890 * Releases handle arrays with pending notifications previously
892 * notifications were not successfully handed over to the guest,
907 * New notifications may have been added while we were not in vmci_ctx_rcv_notifications_release()
909 * doorbell notifications to the old array, and reinstate the in vmci_ctx_rcv_notifications_release()
1033 * allow host side senders of notifications a finer granularity
|
| /Linux-v5.10/include/uapi/linux/usb/ |
| D | cdc.h | 285 * Class-Specific Notifications (6.3) sent by interrupt transfers
287 * section 3.8.2 table 11 of the CDC spec lists Ethernet notifications
288 * section 3.6.2.1 table 5 specifies ACM notifications, accepted by RNDIS
289 * RNDIS also defines its own bit-incompatible notifications
|
