| /linux/drivers/media/pci/cx23885/ |
| H A 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/include/linux/ |
| H A 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
|
| H A D | virtio_pci_modern.h | 13 * @notify_base: Base of vq notifications (non-legacy mode)
14 * @notify_pa: Physical base of vq notifications
18 * @notify_map_cap: Capability for when we need to map notifications per-vq
|
| /linux/Documentation/driver-api/thermal/ |
| H A 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/Documentation/filesystems/ |
| H A 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/Documentation/tee/ |
| H A D | op-tee.rst | 71 OP-TEE notifications
74 There are two kinds of notifications that secure world can use to make
77 1. Synchronous notifications delivered with ``OPTEE_RPC_CMD_NOTIFICATION``
79 2. Asynchronous notifications delivered with a combination of a non-secure
83 Synchronous notifications are limited by depending on RPC for delivery,
85 ``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure
92 multiple notifications.
|
| /linux/tools/testing/selftests/thermal/intel/power_floor/ |
| H A D | power_floor_test.c | 29 perror("Can' disable power floor notifications\n"); in power_floor_exit()
33 printf("Disabled power floor notifications\n"); in power_floor_exit()
59 perror("Can' enable power floor notifications\n"); in main()
65 printf("Enabled power floor notifications\n"); in main()
|
| /linux/Documentation/core-api/ |
| H A 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/Documentation/networking/ |
| H A D | msg_zerocopy.rst | 100 Notifications section in Interface
104 previously passed buffer. It queues completion notifications on the
140 efficient to not wait for notifications, but read without blocking
143 Notifications can be processed out of order with other operations on
145 other operations until the error is read. Zerocopy notifications have
154 a single value, but a range. It coalesces consecutive notifications
166 Ordered delivery is the common case, but not guaranteed. Notifications argument
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A 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/Documentation/arch/s390/ |
| H A 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/Documentation/userspace-api/netlink/ |
| H A 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
438 Multicast notifications
441 One of the strengths of Netlink is the ability to send event notifications
447 notifications about registered families. When a new family is added the
448 sockets subscribed to the notifications will get the following message::
492 To receive notifications the user socket must subscribe to the relevant
510 The socket will now receive notifications.
512 It is recommended to use separate sockets for receiving notifications
[all …]
|
| /linux/Documentation/bpf/ |
| H A 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/arch/x86/include/asm/ |
| H A D | posted_intr.h | 19 u16 notifications; /* Suppress and outstanding bits */ member
87 pi_desc->notifications |= BIT(POSTED_INTR_SN); in __pi_set_sn()
92 pi_desc->notifications &= ~BIT(POSTED_INTR_SN); in __pi_clear_sn()
|
| /linux/tools/net/ynl/lib/ |
| H A D | ynl.h | 111 * ynl_has_ntf() - check if socket has *parsed* notifications
114 * Note that this does not take into account notifications sitting
115 * in netlink socket, just the notifications which have already been
|
| /linux/include/uapi/linux/ |
| H A 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
574 * key. Always present in notifications. Required for all requests (except
578 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
583 * flow. Present in notifications if the stats would be nonzero. Ignored in
586 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| H A D | selinux_netlink.h | 3 * Netlink event notifications for SELinux.
29 #define SELNL_GRP_AVC 0x00000001 /* AVC notifications */
|
| /linux/include/media/i2c/ |
| H A D | bt819.h | 3 bt819.h - bt819 notifications
14 /* v4l2_device notifications. */
|
| /linux/include/xen/interface/hvm/ |
| H A 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/tools/net/ynl/samples/ |
| H A D | netdev.c | 13 * handling, hence the somewhat odd UI. We subscribe to notifications first
15 * notifications as we wait. This allows us to test that YNL can handle
16 * requests and notifications getting interleaved.
|
| /linux/Documentation/power/ |
| H A 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/drivers/rapidio/switches/ |
| H A 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/mm/ |
| H A D | vmpressure.c | 30 * delay the notifications.
357 * vmpressure_register_event() - Bind vmpressure notifications to an eventfd
358 * @memcg: memcg that is interested in vmpressure notifications
359 * @eventfd: eventfd context to link notifications with
363 * infrastructure, so that the notifications will be delivered to the
430 * the vmpressure notifications, and then frees internal resources
|
| /linux/drivers/gpu/drm/radeon/ |
| H A 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/drivers/misc/vmw_vmci/ |
| H A 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.
851 * Retrieves the specified context's pending notifications in the
887 * Releases handle arrays with pending notifications previously
889 * notifications were not successfully handed over to the guest,
904 * New notifications may have been added while we were not in vmci_ctx_rcv_notifications_release()
906 * doorbell notifications to the old array, and reinstate the in vmci_ctx_rcv_notifications_release()
1030 * allow host side senders of notifications a finer granularity
|