| /openbmc/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 …]
|
| /openbmc/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
|
| /openbmc/openbmc/poky/meta/recipes-gnome/libnotify/ |
| H A D | libnotify_0.8.3.bb | 1 SUMMARY = "Library for sending desktop notifications to a notification daemon"
2 DESCRIPTION = "It sends desktop notifications to a notification daemon, as defined \
3 in the Desktop Notifications spec. These notifications can be used to inform \
|
| /openbmc/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
|
| /openbmc/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
434 Multicast notifications
437 One of the strengths of Netlink is the ability to send event notifications
443 notifications about registered families. When a new family is added the
444 sockets subscribed to the notifications will get the following message::
488 To receive notifications the user socket must subscribe to the relevant
506 The socket will now receive notifications.
508 It is recommended to use separate sockets for receiving notifications
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/thunar-volman/ |
| H A D | thunar-volman_4.20.0.bb | 14 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-panel-plugins/places/ |
| H A D | xfce4-places-plugin_1.8.3.bb | 12 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/xfdesktop/ |
| H A D | xfdesktop_4.20.0.bb | 27 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /openbmc/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.
|
| /openbmc/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
|
| /openbmc/openbmc/meta-arm/meta-arm/lib/oeqa/runtime/cases/ |
| H A D | parselogs-ignores-qemuarm64-secureboot.txt | 1 optee: Failed to initialize async notifications: -95
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 10 security notifications and fixes to be available and facilitate coordinated
11 disclosure when notifications and patches/mitigations are available.
|
| /openbmc/linux/Documentation/staging/ |
| H A D | tee.rst | 187 OP-TEE notifications
190 There are two kinds of notifications that secure world can use to make
193 1. Synchronous notifications delivered with ``OPTEE_RPC_CMD_NOTIFICATION``
195 2. Asynchronous notifications delivered with a combination of a non-secure
199 Synchronous notifications are limited by depending on RPC for delivery,
201 ``OPTEE_SMC_CALL_WITH_ARG``. This excludes such notifications from secure
208 multiple notifications.
|
| /openbmc/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::
|
| /openbmc/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
|
| /openbmc/qemu/docs/specs/ |
| H A D | ivshmem-spec.rst | 145 - sends connect notifications for the new client to the other clients
147 - sends connect notifications for the other clients to the new client,
155 notifications to the other clients.
159 If the server terminates without sending disconnect notifications for
199 4. Connect notifications for existing other clients, if any. This is
|
| H A D | vmw_pvscsi-spec.rst | 55 Completion interrupts (completion ring notifications):
60 Message interrupts (message ring notifications):
|
| /openbmc/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
|
| /openbmc/webui-vue/src/assets/styles/bmc/helpers/ |
| H A D | _motion.scss | 5 $duration--slow-01: 400ms; //Large expansion, important system notifications
|
| /openbmc/phosphor-webui/app/common/styles/base/ |
| H A D | variables.scss | 5 $duration--slow-01: 400ms; //Large expansion, important system notifications
|
| /openbmc/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
|
| /openbmc/webui-vue/docs/guide/components/alerts/ |
| H A D | index.md | 5 alerts are not triggered by user action. Success and error notifications based
|
| /openbmc/linux/fs/ecryptfs/ |
| H A D | Kconfig | 18 bool "Enable notifications for userspace key wrap/unwrap"
|
| /openbmc/linux/Documentation/networking/ |
| H A 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
|