drivers/net/wireless/intel/iwlwifi/iwl-phy-db.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/iwl-phy-db.h

Extension

.h

Size

516 bytes

Lines

24

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

• linux/types.h
• iwl-op-mode.h
• iwl-trans.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __IWL_PHYDB_H__
#define __IWL_PHYDB_H__

#include <linux/types.h>

#include "iwl-op-mode.h"
#include "iwl-trans.h"

struct iwl_phy_db *iwl_phy_db_init(struct iwl_trans *trans);

void iwl_phy_db_free(struct iwl_phy_db *phy_db);

int iwl_phy_db_set_section(struct iwl_phy_db *phy_db,
			   struct iwl_rx_packet *pkt);


int iwl_send_phy_db_data(struct iwl_phy_db *phy_db);

#endif /* __IWL_PHYDB_H__ */

Annotation

• Immediate include surface: `linux/types.h`, `iwl-op-mode.h`, `iwl-trans.h`.
• 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.