drivers/net/wireless/intersil/p54/p54spi.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/intersil/p54/p54spi.h

Extension

.h

Size

2631 bytes

Lines

116

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/mutex.h
• linux/list.h
• net/mac80211.h
• p54.h

Detected Declarations

• struct p54s_dma_regs
• struct p54s_tx_info
• struct p54s_priv

Annotated Snippet

struct p54s_dma_regs {
	__le16 cmd;
	__le16 len;
	__le32 addr;
} __packed;

struct p54s_tx_info {
	struct list_head tx_list;
};

struct p54s_priv {
	/* p54_common has to be the first entry */
	struct p54_common common;
	struct ieee80211_hw *hw;
	struct spi_device *spi;

	struct work_struct work;

	struct mutex mutex;
	struct completion fw_comp;

	spinlock_t tx_lock;

	/* protected by tx_lock */
	struct list_head tx_pending;

	enum fw_state fw_state;
	const struct firmware *firmware;

	struct gpio_desc *gpio_powerdown;
	int irq;
};

#endif /* P54SPI_H */

Annotation

• Immediate include surface: `linux/mutex.h`, `linux/list.h`, `net/mac80211.h`, `p54.h`.
• Detected declarations: `struct p54s_dma_regs`, `struct p54s_tx_info`, `struct p54s_priv`.
• 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.