| /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/tools/testing/selftests/drivers/net/netdevsim/ |
| H A D | fib_notifications.sh | 66 check_err $? "$expected_num_lines notifications were expected but $lines were received"
74 check_err $? "Wrong RTM_F_TRAP flags in notifications"
77 check_err $? "Wrong RTM_F_OFFLOAD_FAILED flags in notifications"
119 # Make sure two notifications will be emitted for the programmed route.
124 # notify=2 means emit notifications only for failed route installation,
218 # Make sure two notifications will be emitted for the new route.
223 # notify=2 means emit notifications only for failed route installation,
253 # Make sure two notifications will be emitted for the new route.
259 # notify=2 means emit notifications only for failed route installation,
260 # make sure two notifications will be emitted for the new route.
[all …]
|
| /openbmc/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 | 21 /* Base of vq notifications (non-legacy mode). */
23 /* Physical base of vq notifications */
32 /* Capability for when we need to map notifications per-vq. */
|
| /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,
155 Notifications can be retrieved using ``ynl_ntf_dequeue()`` and have
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/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/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/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/networking/ |
| H A 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
|
| /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)
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::
|
| /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/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/openbmc/meta-openembedded/meta-xfce/recipes-xfce/thunar-volman/ |
| H A D | thunar-volman_4.18.0.bb | 14 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/recipes-xfce/xfdesktop/ |
| H A D | xfdesktop_4.18.1.bb | 26 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | EventDestination.v1_15_0.json | 469 "Kafka": "The destination follows the Kafka protocol for event notifications.",
470 "OEM": "The destination follows an OEM protocol for event notifications.",
471 … "Redfish": "The destination follows the Redfish Specification for event notifications.",
472 "SMTP": "The destination follows the SMTP specification for event notifications.",
473 "SNMPv1": "The destination follows the SNMPv1 protocol for event notifications.",
474 "SNMPv2c": "The destination follows the SNMPv2c protocol for event notifications.",
475 "SNMPv3": "The destination follows the SNMPv3 protocol for event notifications.",
476 "SyslogRELP": "The destination follows syslog RELP for event notifications.",
477 … "SyslogTCP": "The destination follows syslog TCP-based transport for event notifications.",
478 … "SyslogTLS": "The destination follows syslog TLS-based transport for event notifications.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | EventDestination.v1_15_0.json | 469 "Kafka": "The destination follows the Kafka protocol for event notifications.",
470 "OEM": "The destination follows an OEM protocol for event notifications.",
471 … "Redfish": "The destination follows the Redfish Specification for event notifications.",
472 "SMTP": "The destination follows the SMTP specification for event notifications.",
473 "SNMPv1": "The destination follows the SNMPv1 protocol for event notifications.",
474 "SNMPv2c": "The destination follows the SNMPv2c protocol for event notifications.",
475 "SNMPv3": "The destination follows the SNMPv3 protocol for event notifications.",
476 "SyslogRELP": "The destination follows syslog RELP for event notifications.",
477 … "SyslogTCP": "The destination follows syslog TCP-based transport for event notifications.",
478 … "SyslogTLS": "The destination follows syslog TLS-based transport for event notifications.",
[all …]
|
| H A D | NetworkDeviceFunctionMetrics.v1_2_0.json | 127 …scription": "The total number of Congestion Fabric Performance Impact Notifications (FPINs) receiv…
137 …description": "The total number of Delivery Fabric Performance Impact Notifications (FPINs) receiv…
157 …ption": "The total number of Link Integrity Fabric Performance Impact Notifications (FPINs) receiv…
167 …tion": "The total number of Peer Congestion Fabric Performance Impact Notifications (FPINs) receiv…
187 …scription": "The total number of Congestion Fabric Performance Impact Notifications (FPINs) sent.",
197 …description": "The total number of Delivery Fabric Performance Impact Notifications (FPINs) sent.",
217 …ption": "The total number of Link Integrity Fabric Performance Impact Notifications (FPINs) sent.",
227 …tion": "The total number of Peer Congestion Fabric Performance Impact Notifications (FPINs) sent.",
|
| /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/linux/include/media/i2c/ |
| H A D | bt819.h | 3 bt819.h - bt819 notifications
14 /* v4l2_device notifications. */
|
| /openbmc/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.
|
| /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/u-boot/include/ |
| H A D | mailbox.h | 11 * and/or notifications between the CPU on which U-Boot runs and some other
22 * notifications from that entity. The size, content, and format of such
121 * mailbox provider. Providers that solely transfer notifications
139 * notifications will ignore this parameter.
|
| /openbmc/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.
|
| /openbmc/u-boot/include/linux/usb/ |
| H A D | cdc.h | 206 * Class-Specific Notifications (6.3) sent by interrupt transfers
208 * section 3.8.2 table 11 of the CDC spec lists Ethernet notifications
209 * section 3.6.2.1 table 5 specifies ACM notifications, accepted by RNDIS
210 * RNDIS also defines its own bit-incompatible notifications
|