drivers/net/wireless/silabs/wfx/bh.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/silabs/wfx/bh.h

Extension

.h

Size

758 bytes

Lines

35

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• linux/wait.h
• linux/completion.h
• linux/workqueue.h

Detected Declarations

• struct wfx_dev
• struct wfx_hif

Annotated Snippet

struct wfx_hif {
	struct work_struct bh;
	struct completion ctrl_ready;
	wait_queue_head_t tx_buffers_empty;
	atomic_t ctrl_reg;
	int rx_seqnum;
	int tx_seqnum;
	int tx_buffers_used;
};

void wfx_bh_register(struct wfx_dev *wdev);
void wfx_bh_unregister(struct wfx_dev *wdev);
void wfx_bh_request_rx(struct wfx_dev *wdev);
void wfx_bh_request_tx(struct wfx_dev *wdev);
void wfx_bh_poll_irq(struct wfx_dev *wdev);

#endif

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/wait.h`, `linux/completion.h`, `linux/workqueue.h`.
• Detected declarations: `struct wfx_dev`, `struct wfx_hif`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.