| /linux/Documentation/core-api/ |
| H A D | watch_queue.rst | 2 General notification mechanism
5 The general notification mechanism is built on top of the standard pipe driver
6 whereby it effectively splices notification messages from the kernel into pipes
14 "General setup"/"General notification queue"
29 additions to the ring - which might end up interleaved with notification
45 Note that when producing a notification, the kernel does not wait for the
54 Notification messages begin with a short header::
62 "type" indicates the source of the notification record and "subtype" indicates
85 notification producer to indicate some meaning specific to the type and
94 Watch List (Notification Source) API
[all …]
|
| /linux/Documentation/networking/ |
| H A D | msg_zerocopy.rst | 24 notification overhead. As a result, MSG_ZEROCOPY is generally only
34 The kernel returns a notification when it is safe to modify data.
107 The notification itself is a simple scalar value. Each socket
115 Notification Reception
149 Notification Batching
157 When a new notification is about to be queued, it checks whether the
158 new value extends the range of the notification at the tail of the
159 queue. If so, it drops the new notification packet and instead increases
160 the range upper value of the outstanding notification.
163 notification can be squashed into the previous one, so that no more
[all …]
|
| /linux/tools/testing/selftests/drivers/net/netdevsim/ |
| H A D | fib_notifications.sh | 31 # Make sure that the first notification was emitted without
47 # Make sure that the first notification was emitted without RTM_F_TRAP
112 # Make sure a single notification will be emitted for the programmed
125 # make sure a single notification will be emitted for the programmed
165 # Make sure a single notification will be emitted for the deleted route,
212 # Make sure a single notification will be emitted for the new route.
224 # make sure a single notification will be emitted for the new route.
246 # Make sure a single notification will be emitted for the programmed
279 # Make sure a single notification will be emitted for the programmed
291 # make sure a single notification will be emitted for the programmed
[all …]
|
| /linux/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| H A D | time-event.h | 84 * @TE_V1_NOTIF_HOST_EVENT_START: request/receive notification on event start
85 * @TE_V1_NOTIF_HOST_EVENT_END:request/receive notification on event end
88 * @TE_V1_NOTIF_HOST_FRAG_START: request/receive notification on frag start
89 * @TE_V1_NOTIF_HOST_FRAG_END:request/receive notification on frag end
94 * A notification (both event and fragment) includes a status indicating weather
96 * notification the status is always success. There is no start/end fragment
97 * notification for monolithic events.
144 * A notification (both event and fragment) includes a status indicating weather
146 * notification the status is always success. There is no start/end fragment
147 * notification for monolithic events.
[all …]
|
| H A D | offload.h | 16 * @WOWLAN_WAKE_PKT_NOTIFICATION: Notification in &struct iwl_wowlan_wake_pkt_notif
21 * @WOWLAN_INFO_NOTIFICATION: Notification in
28 * @D3_END_NOTIFICATION: End D3 state notification
63 * struct iwl_stored_beacon_notif_v2 - Stored beacon notification
74 * struct iwl_stored_beacon_notif_v3 - Stored beacon notification
|
| /linux/drivers/tee/optee/ |
| H A D | optee_rpc_cmd.h | 31 * Notification from/to secure world.
34 * does a notification wait request instead of spinning in secure world.
35 * Conversely can a synchronous notification can be sent when a secure
38 * This interface can also be used to wait for a asynchronous notification
41 * Waiting on notification
43 * [in] value[0].b notification value
46 * Sending a synchronous notification
48 * [in] value[0].b notification value
|
| /linux/include/uapi/linux/ |
| H A D | watch_queue.h | 9 #define O_NOTIFICATION_PIPE O_EXCL /* Parameter to pipe2() selecting notification pipe */
16 WATCH_TYPE_KEY_NOTIFY = 1, /* Key change event notification */
26 * Notification record header. This is aligned to 64-bits so that subclasses
50 * Notification filtering rules (IOC_WATCH_QUEUE_SET_FILTER).
67 * Extended watch removal notification. This is used optionally if the type
80 * Type of key/keyring change notification.
94 * Key/keyring notification record.
|
| /linux/drivers/soc/fsl/dpio/ |
| H A D | dpio.h | 22 * enum dpio_channel_mode - DPIO notification channel mode
23 * @DPIO_NO_CHANNEL: No support for notification channel
35 * @channel_mode: Notification channel mode
36 * @num_priorities: Number of priorities for the notification channel (1-8);
58 * @channel_mode: Notification channel mode
59 * @num_priorities: Number of priorities for the notification channel (1-8);
|
| /linux/include/uapi/xen/ |
| H A D | gntalloc.h | 57 * Sets up an unmap notification within the page, so that the other side can do
59 * mutexes or close notification on communication channels.
61 * Each mapped page only supports one notification; multiple calls referring to
62 * the same page overwrite the previous notification. You must clear the
63 * notification prior to the IOCTL_GNTALLOC_DEALLOC_GREF if you do not want it
73 * notification we are adjusting.
|
| /linux/drivers/firmware/arm_scmi/ |
| H A D | notify.h | 4 * notification header file containing some definitions, structures
5 * and function prototypes related to SCMI Notification handling.
21 * @max_payld_sz: Max possible size for the payload of a notification message
22 * @max_report_sz: Max possible size for the report of a notification message
37 * struct scmi_event_ops - Protocol helpers called by the notification core.
38 * @is_notify_supported: Return 0 if the specified notification for the
|
| H A D | notify.c | 3 * System Control and Management Interface (SCMI) Notification support
11 * interested agents via notification messages: this is an implementation
15 * An SCMI Notification core instance is initialized for each active platform
25 * events' delivery using the standard Kernel notification chains machinery.
28 * of the SCMI Protocol itself, the underlying notification chains are created
36 * All users provided callbacks and allocated notification-chains are stored in
42 * and is served by its own dedicated notification chain; information contained
51 * Upon reception of a notification message from the platform the SCMI RX ISR
59 * queued items into the proper notification-chain: notifications processing can
64 * Events' information is then extracted from the SCMI Notification messages and
[all …]
|
| H A D | scmi_power_control.c | 9 * shutdowns or cold/warm resets) we register an SCMI Notification notifier
12 * Once such a notification is received we act accordingly to perform the
42 * this driver and the shutdown/reboot is started, any further notification
76 * SCMI SystemPower notification
78 * notification to start the needed userspace interactions.
267 * @event: The SystemPower notification event id
274 * other following SystemPower notification received from the same SCMI
294 dev_err(sc->dev, "Ignoring forceful notification.\n"); in scmi_userspace_notifier()
|
| /linux/Documentation/power/ |
| H A D | pm_qos_interface.rst | 40 value and recompute the new aggregated target, calling the notification tree
45 and call the notification tree if the target was changed as a result of
56 Adds a notification callback function to the CPU latency QoS. The callback is
60 Removes the notification callback function from the CPU latency QoS.
115 value and recompute the new aggregated target, calling the notification
120 and call the notification trees if the target was changed as a result of
166 Notification mechanisms:
168 The per-device PM QoS framework has a per-device notification tree.
171 Adds a notification callback function for the device for a particular request
178 Removes the notification callback function for the device.
|
| /linux/net/sctp/ |
| H A D | ulpevent.c | 109 * provided by this notification.
128 * head room to use as notification. in sctp_ulpevent_make_assoc_change()
140 /* Include the notification structure */ in sctp_ulpevent_make_assoc_change()
186 * This field is the total length of the notification data, including in sctp_ulpevent_make_assoc_change()
187 * the notification header. in sctp_ulpevent_make_assoc_change()
272 * This field is the total length of the notification data, including in sctp_ulpevent_make_peer_addr_change()
273 * the notification header. in sctp_ulpevent_make_peer_addr_change()
358 /* Create and initialize an SCTP_REMOTE_ERROR notification.
393 * notification with. in sctp_ulpevent_make_remote_error()
425 /* Create and initialize a SCTP_SEND_FAILED notification.
[all …]
|
| /linux/include/sound/sof/ipc4/ |
| H A D | header.h | 123 /* Notification (FW to SW driver) */
463 /* Notification messages */
467 * bit 0-15: notification type specific
488 /* Value of notification type field - must fit into 8 bits */
490 /* Phrase detected (notification from WoV module) */
505 /* Custom module notification */
542 * struct sof_ipc4_notify_module_data - payload for module notification
543 * @instance_id: instance ID of the originator module of the notification
544 * @module_id: module ID of the originator of the notification
547 * @event_data: Optional notification data, module and notification dependent
[all …]
|
| /linux/Documentation/wmi/ |
| H A D | acpi-interface.rst | 32 0x10 2 2 character method ID or single byte notification ID.
37 The WMI object flags control whether the method or notification ID is used:
42 - 0x8: Data block describes a WMI event, use notification ID instead
46 The method/notification ID is used to construct the ACPI method names used for
81 the ACPI method are the notification ID of the data block describing the WMI
96 holding the notification ID of the event. This method should be evaluated every
97 time an ACPI notification is received, since some ACPI implementations use a
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fc_host | 5 These files contain the number of congestion notification
7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| H A D | sysfs-class-fc_remote_ports | 5 These files contain the number of congestion notification
7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| /linux/fs/notify/ |
| H A D | notification.c | 7 * Basic idea behind the notification queue: An fsnotify group (like inotify)
8 * sends the userspace notification about events asynchronously some time after
11 * multiple group's notification queues we can't add the event directly to each
14 * going to end up on one, and only one, notification queue we embed one
71 * Try to add an event to the notification queue.
145 * Return the first event on the notification list without removing it.
160 * Remove and return the first event from the notification list. It is the
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 32 the lid state upon the last lid notification instead of returning the lid
43 changed to "opened". Thus the "opened" notification is not guaranteed. But
45 state is changed to "closed". The "closed" notification is normally used to
71 events and the unreliable initial state notification, Linux users can use
82 notification is missing.
93 control method is not reliable and the initial lid state notification is
97 and the unreliable initial state notification, Linux users should always
|
| /linux/drivers/soc/qcom/ |
| H A D | pmic_glink_altmode.c | 48 __le32 notification; member
263 u32 notification; in pmic_glink_altmode_sc8180xp_notify() local
278 notification = le32_to_cpu(msg->notification); in pmic_glink_altmode_sc8180xp_notify()
279 port = FIELD_GET(SC8180X_PORT_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
280 orientation = FIELD_GET(SC8180X_ORIENTATION_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
281 mux = FIELD_GET(SC8180X_MUX_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
282 mode = FIELD_GET(SC8180X_MODE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
283 hpd_state = FIELD_GET(SC8180X_HPD_STATE_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
284 hpd_irq = FIELD_GET(SC8180X_HPD_IRQ_MASK, notification); in pmic_glink_altmode_sc8180xp_notify()
289 dev_dbg(altmode->dev, "notification on undefined port %d\n", port); in pmic_glink_altmode_sc8180xp_notify()
[all …]
|
| /linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 15 By design, a FAN_FS_ERROR notification exposes sufficient information
26 error that occurred for a file system since the last notification, and
36 A FAN_FS_ERROR Notification has the following format::
40 [ Notification Metadata (Mandatory) ]
69 notification.
|
| /linux/drivers/misc/vmw_vmci/ |
| H A D | vmci_doorbell.c | 30 * DoorbellEntry describes the a doorbell notification handle allocated by the
69 * the case where multiple handles share a notification index, we hand out
147 * Below we try to allocate an index in the notification in dbell_index_table_add()
207 * notification index, we take the opportunity to in dbell_index_table_remove()
226 * index in the bitmap in the device backend. A notification state
245 * the device backend. The notification state is destroyed in hypervisor.
262 * host via the hypervisor with the notification info.
290 * Dispatches a doorbell notification to the host context.
324 * Register the notification bitmap with the host.
343 pr_devel("Failed to register (PPN=%llu) as notification bitmap (error=%d)\n", in vmci_dbell_register_notification_bitmap()
[all …]
|
| /linux/Documentation/filesystems/ |
| H A D | dnotify.rst | 4 Linux Directory Notification
9 The intention of directory notification is to allow user applications
11 The basic mechanism involves the application registering for notification
28 Usually, the application must reregister after each notification, but
46 The notification should work for any local access to files even if the
|
| /linux/Documentation/ABI/stable/ |
| H A D | thermal-notification | 1 What: A notification mechanism for thermal related events
3 This interface enables notification for thermal related events.
4 The notification is in the form of a netlink event.
|