drivers/net/wireless/intel/iwlwifi/mvm/time-sync.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/mvm/time-sync.h

Extension

.h

Size

866 bytes

Lines

31

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

• mvm.h
• linux/ieee80211.h

Detected Declarations

• function iwl_mvm_time_sync_frame

Annotated Snippet

#ifndef __TIME_SYNC_H__
#define __TIME_SYNC_H__

#include "mvm.h"
#include <linux/ieee80211.h>

void iwl_mvm_init_time_sync(struct iwl_time_sync_data *data);
void iwl_mvm_time_sync_msmt_event(struct iwl_mvm *mvm,
				  struct iwl_rx_cmd_buffer *rxb);
void iwl_mvm_time_sync_msmt_confirm_event(struct iwl_mvm *mvm,
					  struct iwl_rx_cmd_buffer *rxb);
int iwl_mvm_time_sync_config(struct iwl_mvm *mvm, const u8 *addr,
			     u32 protocols);

static inline
bool iwl_mvm_time_sync_frame(struct iwl_mvm *mvm, struct sk_buff *skb, u8 *addr)
{
	if (ether_addr_equal(mvm->time_sync.peer_addr, addr) &&
	    (ieee80211_is_timing_measurement(skb) || ieee80211_is_ftm(skb))) {
		skb_queue_tail(&mvm->time_sync.frame_list, skb);
		return true;
	}

	return false;
}
#endif

Annotation

• Immediate include surface: `mvm.h`, `linux/ieee80211.h`.
• Detected declarations: `function iwl_mvm_time_sync_frame`.
• 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.