/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/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/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/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/userspace-api/netlink/ |
H A D | intro-specs.rst | 24 - ``--subscribe $group`` - receive notifications from ``$group`` 142 YNL notifications 145 YNL lib supports using the same socket for notifications and 146 requests. In case notifications arrive during processing of a request 149 To subscribed to notifications use ``ynl_subscribe()``. 150 The notifications have to be read out from the socket, 157 type upfront the notifications are returned as ``struct ynl_ntf_base_type *``
|
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/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/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/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/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) 299 It can then be set to receive keyring change notifications:: 303 The notifications can then be consumed by something like the following::
|
H A D | netlink.rst | 26 Use separate command IDs for notifications. This makes it easier to 27 sort the notifications from replies (and present them to the user
|
/linux/tools/testing/selftests/net/packetdrill/ |
H A D | tcp_zerocopy_batch.pkt | 4 // send multiple packets, then read one range of all notifications.
|
/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/drivers/virtio/ |
H A 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/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/fs/ecryptfs/ |
H A D | Kconfig | 18 bool "Enable notifications for userspace key wrap/unwrap"
|
/linux/Documentation/networking/ |
H A D | msg_zerocopy.rst | 104 previously passed buffer. It queues completion notifications on the 140 efficient to not wait for notifications, but read without blocking 145 other operations until the error is read. Zerocopy notifications have 154 a single value, but a range. It coalesces consecutive notifications
|
H A D | nexthop-group-resilient.rst | 135 - Single-bucket notifications of the type 136 ``NH_NOTIFIER_INFO_TYPE_RES_BUCKET``, which is used for notifications of 143 Some single-bucket notifications are forced, as indicated by the "force" 148 Non-forced notifications can be overridden by the driver by returning an
|
/linux/Documentation/networking/device_drivers/ethernet/marvell/ |
H A D | octeon_ep.rst | 39 Octeon device processes them. The firmware also sends unsolicited notifications
|
/linux/drivers/thermal/intel/ |
H A D | Kconfig | 31 two trip points which can be set by user to get notifications via thermal 54 be set by user mode programs to get notifications via Linux thermal
|
/linux/drivers/soc/fsl/dpio/ |
H A D | dpio-service.c | 30 struct list_head notifications; member 171 INIT_LIST_HEAD(&obj->notifications); in dpaa2_io_create() 315 list_add(&ctx->node, &d->notifications); in dpaa2_io_service_register()
|
/linux/Documentation/fb/ |
H A 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/kernel/ |
H A D | seccomp.c | 155 struct list_head notifications; member 1138 list_add_tail(&n.list, &match->notif->notifications); in seccomp_do_user_notification() 1433 list_for_each_entry(knotif, &filter->notif->notifications, list) { in seccomp_notify_detach() 1470 list_for_each_entry(cur, &filter->notif->notifications, list) { in find_notification() 1536 list_for_each_entry(cur, &filter->notif->notifications, list) { in seccomp_notify_recv() 1830 list_for_each_entry(cur, &filter->notif->notifications, list) { in seccomp_notify_poll() 1864 INIT_LIST_HEAD(&filter->notif->notifications); in init_listener()
|
/linux/security/keys/ |
H A D | Kconfig | 129 bool "Provide key/keyring change notifications" 132 This option provides support for getting change notifications
|
/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
H A 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
|