drivers/net/wireless/mediatek/mt76/mt76x0/mcu.h

File Facts

System

Linux kernel

Corpus path

drivers/net/wireless/mediatek/mt76/mt76x0/mcu.h

Extension

.h

Size

944 bytes

Lines

47

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

• ../mt76x02_mcu.h

Detected Declarations

• struct mt76x02_dev
• enum mcu_calibrate
• function mt76x0_firmware_running

Annotated Snippet

#ifndef __MT76X0U_MCU_H
#define __MT76X0U_MCU_H

#include "../mt76x02_mcu.h"

struct mt76x02_dev;

#define MT_MCU_IVB_SIZE			0x40
#define MT_MCU_DLM_OFFSET		0x80000

/* We use same space for BBP as for MAC regs
 * #define MT_MCU_MEMMAP_BBP		0x40000000
 */
#define MT_MCU_MEMMAP_RF		0x80000000

enum mcu_calibrate {
	MCU_CAL_R = 1,
	MCU_CAL_RXDCOC,
	MCU_CAL_LC,
	MCU_CAL_LOFT,
	MCU_CAL_TXIQ,
	MCU_CAL_BW,
	MCU_CAL_DPD,
	MCU_CAL_RXIQ,
	MCU_CAL_TXDCOC,
	MCU_CAL_RX_GROUP_DELAY,
	MCU_CAL_TX_GROUP_DELAY,
	MCU_CAL_VCO,
	MCU_CAL_NO_SIGNAL = 0xfe,
	MCU_CAL_FULL = 0xff,
};

int mt76x0e_mcu_init(struct mt76x02_dev *dev);
int mt76x0u_mcu_init(struct mt76x02_dev *dev);
static inline int mt76x0_firmware_running(struct mt76x02_dev *dev)
{
	return mt76_rr(dev, MT_MCU_COM_REG0) == 1;
}

#endif

Annotation

• Immediate include surface: `../mt76x02_mcu.h`.
• Detected declarations: `struct mt76x02_dev`, `enum mcu_calibrate`, `function mt76x0_firmware_running`.
• 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.