drivers/net/wireless/intel/iwlwifi/fw/pnvm.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intel/iwlwifi/fw/pnvm.h

Extension

.h

Size

698 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

• iwl-drv.h
• fw/notif-wait.h
• fw/img.h

Detected Declarations

• function iwl_pnvm_get_fs_name

Annotated Snippet

#ifndef __IWL_PNVM_H__
#define __IWL_PNVM_H__

#include "iwl-drv.h"
#include "fw/notif-wait.h"
#include "fw/img.h"

#define MVM_UCODE_PNVM_TIMEOUT	(HZ / 4)

#define MAX_PNVM_NAME  64

int iwl_pnvm_load(struct iwl_trans *trans,
		  struct iwl_notif_wait_data *notif_wait,
		  const struct iwl_fw *fw, __le32 sku_id[3]);

static inline
void iwl_pnvm_get_fs_name(struct iwl_trans *trans,
			  u8 *pnvm_name, size_t max_len)
{
	char _fw_name_pre[FW_NAME_PRE_BUFSIZE];

	snprintf(pnvm_name, max_len, "%s.pnvm",
		 iwl_drv_get_fwname_pre(trans, _fw_name_pre));
}

#endif /* __IWL_PNVM_H__ */

Annotation

• Immediate include surface: `iwl-drv.h`, `fw/notif-wait.h`, `fw/img.h`.
• Detected declarations: `function iwl_pnvm_get_fs_name`.
• 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.