drivers/net/wireless/quantenna/qtnfmac/trans.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/quantenna/qtnfmac/trans.h

Extension

.h

Size

1142 bytes

Lines

45

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/kernel.h
• linux/module.h
• linux/skbuff.h
• linux/mutex.h
• qlink.h

Detected Declarations

• struct qtnf_bus
• struct qtnf_cmd_ctl_node
• struct qtnf_qlink_transport

Annotated Snippet

struct qtnf_cmd_ctl_node {
	struct completion cmd_resp_completion;
	struct sk_buff *resp_skb;
	u16 seq_num;
	bool waiting_for_resp;
	spinlock_t resp_lock; /* lock for resp_skb & waiting_for_resp changes */
};

struct qtnf_qlink_transport {
	struct qtnf_cmd_ctl_node curr_cmd;
	struct sk_buff_head event_queue;
	size_t event_queue_max_len;
};

void qtnf_trans_init(struct qtnf_bus *bus);
void qtnf_trans_free(struct qtnf_bus *bus);

int qtnf_trans_send_next_cmd(struct qtnf_bus *bus);
int qtnf_trans_handle_rx_ctl_packet(struct qtnf_bus *bus, struct sk_buff *skb);
int qtnf_trans_send_cmd_with_resp(struct qtnf_bus *bus,
				  struct sk_buff *cmd_skb,
				  struct sk_buff **response_skb);

#endif /* _QTN_FMAC_TRANS_H_ */

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/skbuff.h`, `linux/mutex.h`, `qlink.h`.
• Detected declarations: `struct qtnf_bus`, `struct qtnf_cmd_ctl_node`, `struct qtnf_qlink_transport`.
• 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.