drivers/net/wireless/ti/wlcore/vendor_cmd.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/ti/wlcore/vendor_cmd.h

Extension

.h

Size

924 bytes

Lines

43

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

• No C-style include directives detected by the generator.

Detected Declarations

• enum wlcore_vendor_commands
• enum wlcore_vendor_attributes
• enum wlcore_vendor_events

Annotated Snippet

#ifndef __WLCORE_VENDOR_H__
#define __WLCORE_VENDOR_H__

#ifdef __KERNEL__
void wlcore_set_vendor_commands(struct wiphy *wiphy);
#endif

#define TI_OUI	0x080028

enum wlcore_vendor_commands {
	WLCORE_VENDOR_CMD_SMART_CONFIG_START,
	WLCORE_VENDOR_CMD_SMART_CONFIG_STOP,
	WLCORE_VENDOR_CMD_SMART_CONFIG_SET_GROUP_KEY,

	NUM_WLCORE_VENDOR_CMD,
	MAX_WLCORE_VENDOR_CMD = NUM_WLCORE_VENDOR_CMD - 1
};

enum wlcore_vendor_attributes {
	WLCORE_VENDOR_ATTR_FREQ,
	WLCORE_VENDOR_ATTR_PSK,
	WLCORE_VENDOR_ATTR_SSID,
	WLCORE_VENDOR_ATTR_GROUP_ID,
	WLCORE_VENDOR_ATTR_GROUP_KEY,

	NUM_WLCORE_VENDOR_ATTR,
	MAX_WLCORE_VENDOR_ATTR = NUM_WLCORE_VENDOR_ATTR - 1
};

enum wlcore_vendor_events {
	WLCORE_VENDOR_EVENT_SC_SYNC,
	WLCORE_VENDOR_EVENT_SC_DECODE,
};

#endif /* __WLCORE_VENDOR_H__ */

Annotation

• Detected declarations: `enum wlcore_vendor_commands`, `enum wlcore_vendor_attributes`, `enum wlcore_vendor_events`.
• 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.