| /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/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/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/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/ |
| 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)
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/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/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/fs/ecryptfs/ |
| D | Kconfig | 18 bool "Enable notifications for userspace key wrap/unwrap"
|
| /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/kernel/ |
| D | seccomp.c | 143 struct list_head notifications; member
862 list_add(&n.list, &match->notif->notifications); in seccomp_do_user_notification()
1134 list_for_each_entry(knotif, &filter->notif->notifications, list) { in seccomp_notify_detach()
1171 list_for_each_entry(cur, &filter->notif->notifications, list) { in find_notification()
1201 list_for_each_entry(cur, &filter->notif->notifications, list) { in seccomp_notify_recv()
1452 list_for_each_entry(cur, &filter->notif->notifications, list) { in seccomp_notify_poll()
1487 INIT_LIST_HEAD(&filter->notif->notifications); in init_listener()
|
| /Linux-v5.10/drivers/soc/fsl/dpio/ |
| D | dpio-service.c | 29 struct list_head notifications; member
141 INIT_LIST_HEAD(&obj->notifications); in dpaa2_io_create()
277 list_add(&ctx->node, &d->notifications); in dpaa2_io_service_register()
|
| /Linux-v5.10/Documentation/networking/ |
| D | msg_zerocopy.rst | 103 previously passed buffer. It queues completion notifications on the
139 efficient to not wait for notifications, but read without blocking
144 other operations until the error is read. Zerocopy notifications have
153 a single value, but a range. It coalesces consecutive notifications
|
| /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
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/fb/ |
| D | udlfb.rst | 47 Accurate damage/changed area notifications work around this problem.
69 application must send down damage notifications to trigger repaints of the
80 framebuffers that need damage info). These damage notifications allow
|
| /Linux-v5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_acpi.c | 64 struct amdgpu_atif_notifications notifications; member
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/security/keys/ |
| D | Kconfig | 119 bool "Provide key/keyring change notifications"
122 This option provides support for getting change notifications on keys
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | ethernet-driver.rst | 105 availability notifications and buffer pool management. DPIOs are shared between
115 is sent to the CPU; notifications are raised per channel, so even if multiple
|
| D | dpio-driver.rst | 35 B. allow drivers to register callbacks for data availability notifications
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-uwb_rc-wusbhc | 48 notifications to the host.
|
| /Linux-v5.10/Documentation/hwmon/ |
| D | acpi_power_meter.rst | 47 There are a few other ACPI notifications that can be sent by the firmware. In
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/ |
| D | xen.txt | 16 - interrupts: the interrupt used by Xen to inject event notifications.
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | radeon_acpi.c | 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/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smsm.txt | 6 matrix of bitmaps signal subscription of notifications upon changes to a
|
| /Linux-v5.10/Documentation/devicetree/bindings/usb/ |
| D | msm-hsusb.txt | 48 - qcom,otg-control: OTG control (VBUS and ID notifications) can be one of
|
