| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Notification-Packets.html | 75 <p>The <small>GDB</small> remote serial protocol includes <em>notifications</em>,
77 may send notifications (although the only notifications defined at
78 present are sent by the stub). Notifications carry information
94 <p>Recipients should silently ignore corrupted notifications and
95 notifications they do not understand. Recipients should restart
99 <p>Senders should only send the notifications described here when this
101 future, we may extend the protocol to permit existing notifications in
107 transmit notifications without fear of confusing older clients. There
108 are no notifications defined for <small>GDB</small> to send at the moment, but we
139 <p>Specifically, notifications may appear when <small>GDB</small> is not
[all …]
|
| H A D | GDB_002fMI-General-Design.html | 76 and notifications. Each command results in exactly one response,
81 Notifications is the mechanism for reporting changes in the state of the
85 <p>The important examples of notifications are:
87 <li> Exec notifications. These are used to report changes in
95 </li><li> Console output, and status notifications. Console output
96 notifications are used to report output of CLI commands, as well as
97 diagnostics for other commands. Status notifications are used to
102 </li><li> General notifications. Commands may have various side effects on
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Notification-Packets.html | 75 <p>The <small>GDB</small> remote serial protocol includes <em>notifications</em>,
77 may send notifications (although the only notifications defined at
78 present are sent by the stub). Notifications carry information
94 <p>Recipients should silently ignore corrupted notifications and
95 notifications they do not understand. Recipients should restart
99 <p>Senders should only send the notifications described here when this
101 future, we may extend the protocol to permit existing notifications in
107 transmit notifications without fear of confusing older clients. There
108 are no notifications defined for <small>GDB</small> to send at the moment, but we
139 <p>Specifically, notifications may appear when <small>GDB</small> is not
[all …]
|
| H A D | GDB_002fMI-General-Design.html | 76 and notifications. Each command results in exactly one response,
81 Notifications is the mechanism for reporting changes in the state of the
85 <p>The important examples of notifications are:
87 <li> Exec notifications. These are used to report changes in
95 </li><li> Console output, and status notifications. Console output
96 notifications are used to report output of CLI commands, as well as
97 diagnostics for other commands. Status notifications are used to
102 </li><li> General notifications. Commands may have various side effects on
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-gnome/libnotify/ |
| H A D | libnotify_0.7.9.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 \
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/ |
| 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::
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/linux/ |
| H A D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
74 * datapath. Always present in notifications.
76 * datapath. Always present in notifications.
137 /* Kernel-to-user notifications. */
147 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
152 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
523 * key. Always present in notifications. Required for all requests (except
527 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
532 * flow. Present in notifications if the stats would be nonzero. Ignored in
535 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/linux/ |
| H A D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
74 * datapath. Always present in notifications.
76 * datapath. Always present in notifications.
137 /* Kernel-to-user notifications. */
147 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
152 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
523 * key. Always present in notifications. Required for all requests (except
527 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
532 * flow. Present in notifications if the stats would be nonzero. Ignored in
535 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/include/uapi/linux/ |
| H A D | openvswitch.h | 66 * the &struct ovs_header. Always present in notifications. Required in
74 * datapath. Always present in notifications.
76 * datapath. Always present in notifications.
141 /* Kernel-to-user notifications. */
151 * @OVS_PACKET_ATTR_PACKET: Present for all notifications. Contains the entire
156 * @OVS_PACKET_ATTR_KEY: Present for all notifications. Contains the flow key
533 * key. Always present in notifications. Required for all requests (except
537 * notifications. Required for %OVS_FLOW_CMD_NEW requests, optional for
542 * flow. Present in notifications if the stats would be nonzero. Ignored in
545 * TCP flags seen on packets in this flow. Only present in notifications for
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/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.
|
| /OK3568_Linux_fs/u-boot/include/ |
| H A D | mailbox.h | 12 * and/or notifications between the CPU on which U-Boot runs and some other
23 * notifications from that entity. The size, content, and format of such
123 * mailbox provider. Providers that solely transfer notifications
141 * notifications will ignore this parameter.
|
| /OK3568_Linux_fs/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
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H A D | userfaultfd.rst | 66 events, except page fault notifications, may be generated:
159 Write Protect Notifications
258 the same read(2) protocol as for the page fault notifications. The
270 enable notifications about mremap() calls. When the
277 enable notifications about madvise(MADV_REMOVE) and
283 enable notifications about memory unmapping. The manager will
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/recipes-xfce/thunar-volman/ |
| H A D | thunar-volman_4.16.0.bb | 14 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/recipes-xfce/xfdesktop/ |
| H A D | xfdesktop_4.16.0.bb | 14 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|
| /OK3568_Linux_fs/kernel/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()
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/recipes-panel-plugins/places/ |
| H A D | xfce4-places-plugin_1.8.1.bb | 13 PACKAGECONFIG[notify] = "--enable-notifications,--disable-notifications,libnotify"
|