drivers/net/wireless/intel/iwlwifi/mld/notif.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/mld/notif.h

Extension

.h

Size

1052 bytes

Lines

37

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct iwl_mld
• enum iwl_mld_object_type

Annotated Snippet

#ifndef __iwl_mld_notif_h__
#define __iwl_mld_notif_h__

struct iwl_mld;

void iwl_mld_rx(struct iwl_op_mode *op_mode, struct napi_struct *napi,
		struct iwl_rx_cmd_buffer *rxb);

void iwl_mld_rx_rss(struct iwl_op_mode *op_mode, struct napi_struct *napi,
		    struct iwl_rx_cmd_buffer *rxb, unsigned int queue);

void iwl_mld_async_handlers_wk(struct wiphy *wiphy, struct wiphy_work *wk);

void iwl_mld_cancel_async_notifications(struct iwl_mld *mld);

enum iwl_mld_object_type {
	IWL_MLD_OBJECT_TYPE_NONE,
	IWL_MLD_OBJECT_TYPE_LINK,
	IWL_MLD_OBJECT_TYPE_STA,
	IWL_MLD_OBJECT_TYPE_VIF,
	IWL_MLD_OBJECT_TYPE_ROC,
	IWL_MLD_OBJECT_TYPE_SCAN,
	IWL_MLD_OBJECT_TYPE_FTM_REQ,
	IWL_MLD_OBJECT_TYPE_NAN,
};

void iwl_mld_cancel_notifications_of_object(struct iwl_mld *mld,
					    enum iwl_mld_object_type obj_type,
					    u32 obj_id);
void iwl_mld_delete_handlers(struct iwl_mld *mld, const u16 *cmds, int n_cmds);

#endif /* __iwl_mld_notif_h__ */

Annotation

• Detected declarations: `struct iwl_mld`, `enum iwl_mld_object_type`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.