drivers/net/wireless/intel/iwlwifi/mld/time_sync.h
Source file repositories/reference/linux-study-clean/drivers/net/wireless/intel/iwlwifi/mld/time_sync.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/wireless/intel/iwlwifi/mld/time_sync.h- Extension
.h- Size
- 830 bytes
- Lines
- 27
- 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_time_sync_data
Annotated Snippet
struct iwl_mld_time_sync_data {
struct rcu_head rcu_head;
u8 peer_addr[ETH_ALEN];
u32 active_protocols;
struct sk_buff_head frame_list;
};
int iwl_mld_time_sync_config(struct iwl_mld *mld, const u8 *addr,
u32 protocols);
int iwl_mld_time_sync_fw_config(struct iwl_mld *mld);
void iwl_mld_deinit_time_sync(struct iwl_mld *mld);
void iwl_mld_handle_time_msmt_notif(struct iwl_mld *mld,
struct iwl_rx_packet *pkt);
bool iwl_mld_time_sync_frame(struct iwl_mld *mld, struct sk_buff *skb,
u8 *addr);
void iwl_mld_handle_time_sync_confirm_notif(struct iwl_mld *mld,
struct iwl_rx_packet *pkt);
#endif /* __iwl_mld_time_sync_h__ */
Annotation
- Detected declarations: `struct iwl_mld_time_sync_data`.
- 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.