| /Documentation/driver-api/thermal/ |
| 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
|
| /Documentation/userspace-api/netlink/ |
| 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 *``
|
| 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 …]
|
| D | specs.rst | 279 There are three types of entries in this section - operations, notifications
294 Notifications and events both refer to the asynchronous messages sent by
298 This arrangement is commonly used for notifications about
304 property. Events are considered less idiomatic for netlink and notifications
311 operations, notifications etc.
|
| D | genetlink-legacy.rst | 109 responses share the same message ID. Notifications have separate
146 For notifications the ``value`` is provided at the op level but it
|
| /Documentation/filesystems/ |
| 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
|
| /Documentation/arch/s390/ |
| 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.
|
| /Documentation/tee/ |
| 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.
|
| /Documentation/firmware-guide/acpi/ |
| 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
|
| /Documentation/networking/ |
| 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
|
| D | rds.rst | 121 notifications via control messages (for instance, there is a
123 operation completes). These notifications are received through
144 this - by using congestion notifications, and by checking for
178 Congestion Notifications
|
| 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
|
| /Documentation/core-api/ |
| 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::
|
| 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
|
| /Documentation/bpf/ |
| 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
|
| /Documentation/power/ |
| 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
|
| /Documentation/netlink/specs/ |
| D | ovs_flow.yaml | 386 notifications. Required for all requests (except dumps).
393 match the key. Always present in notifications. Required for
403 Statistics for this flow. Present in notifications if the stats would
410 packets in this flow. Only present in notifications for TCP flows, and
418 flow. Only present in notifications if a packet has been processed for
426 ignored in requests. Never present in notifications.
450 requests. Present in notifications if the flow was created with this
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 99 events, except page fault notifications, may be generated:
195 Write Protect Notifications
369 the same read(2) protocol as for the page fault notifications. The
381 enable notifications about mremap() calls. When the
388 enable notifications about madvise(MADV_REMOVE) and
394 enable notifications about memory unmapping. The manager will
|
| /Documentation/fb/ |
| 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
|
| /Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeon_ep.rst | 39 Octeon device processes them. The firmware also sends unsolicited notifications
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 47 There are a few other ACPI notifications that can be sent by the firmware. In
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | fsl,qman.yaml | 17 as RED/WRED, congestion notifications and tail discards. This binding covers the
|
| /Documentation/driver-api/ |
| D | dpll.rst | 413 Notifications chapter
416 dpll device can provide notifications regarding status changes of the
421 Notifications messages:
467 Notifications of adding or removing dpll devices are created within
469 Notifications about registering/deregistering pins are also invoked by
471 Notifications about status changes either of dpll device or a pin are
|
| D | wbrf.rst | 20 * Consumers with this _DSM will be able to register for notifications of
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 34 notifications is Ext4.
|