drivers/mfd/wm5110-tables.c

Source file repositories/reference/linux-study-clean/drivers/mfd/wm5110-tables.c

File Facts

System: Linux kernel
Corpus path: drivers/mfd/wm5110-tables.c
Extension: .c
Size: 137858 bytes
Lines: 3226
Domain: Driver Families
Bucket: drivers/mfd
Inferred role: Driver Families: exported/initcall integration point
Status: integration 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.
Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/module.h
linux/mfd/arizona/core.h
linux/mfd/arizona/registers.h
linux/device.h
arizona.h

Detected Declarations

function wm5110_patch
function wm5110_is_rev_b_adsp_memory
function wm5110_is_rev_d_adsp_memory
function wm5110_is_adsp_memory
function wm5110_readable_register
function wm5110_volatile_register
export wm5110_patch
export wm5110_aod
export wm5110_irq
export wm5110_revd_irq
export wm5110_spi_regmap
export wm5110_i2c_regmap

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-only
/*
 * wm5110-tables.c  --  WM5110 data tables
 *
 * Copyright 2012 Wolfson Microelectronics plc
 *
 * Author: Mark Brown <broonie@opensource.wolfsonmicro.com>
 */

#include <linux/module.h>

#include <linux/mfd/arizona/core.h>
#include <linux/mfd/arizona/registers.h>
#include <linux/device.h>

#include "arizona.h"

#define WM5110_NUM_AOD_ISR 2
#define WM5110_NUM_ISR 5

static const struct reg_sequence wm5110_reva_patch[] = {
	{ 0x80, 0x3 },
	{ 0x44, 0x20 },
	{ 0x45, 0x40 },
	{ 0x46, 0x60 },
	{ 0x47, 0x80 },
	{ 0x48, 0xa0 },
	{ 0x51, 0x13 },
	{ 0x52, 0x33 },
	{ 0x53, 0x53 },
	{ 0x54, 0x73 },
	{ 0x55, 0x75 },
	{ 0x56, 0xb3 },
	{ 0x2ef, 0x124 },
	{ 0x2ef, 0x124 },
	{ 0x2f0, 0x124 },
	{ 0x2f0, 0x124 },
	{ 0x2f1, 0x124 },
	{ 0x2f1, 0x124 },
	{ 0x2f2, 0x124 },
	{ 0x2f2, 0x124 },
	{ 0x2f3, 0x124 },
	{ 0x2f3, 0x124 },
	{ 0x2f4, 0x124 },
	{ 0x2f4, 0x124 },
	{ 0x2eb, 0x60 },
	{ 0x2ec, 0x60 },
	{ 0x2ed, 0x60 },
	{ 0xc30, 0x3e3e },
	{ 0xc30, 0x3e3e },
	{ 0xc31, 0x3e },
	{ 0xc32, 0x3e3e },
	{ 0xc32, 0x3e3e },
	{ 0xc33, 0x3e3e },
	{ 0xc33, 0x3e3e },
	{ 0xc34, 0x3e3e },
	{ 0xc34, 0x3e3e },
	{ 0xc35, 0x3e3e },
	{ 0xc35, 0x3e3e },
	{ 0xc36, 0x3e3e },
	{ 0xc36, 0x3e3e },
	{ 0xc37, 0x3e3e },
	{ 0xc37, 0x3e3e },
	{ 0xc38, 0x3e3e },
	{ 0xc38, 0x3e3e },
	{ 0xc30, 0x3e3e },
	{ 0xc30, 0x3e3e },
	{ 0xc39, 0x3e3e },
	{ 0xc39, 0x3e3e },
	{ 0xc3a, 0x3e3e },
	{ 0xc3a, 0x3e3e },
	{ 0xc3b, 0x3e3e },
	{ 0xc3b, 0x3e3e },
	{ 0xc3c, 0x3e },
	{ 0x201, 0x18a5 },
	{ 0x201, 0x18a5 },
	{ 0x201, 0x18a5 },
	{ 0x202, 0x4100 },
	{ 0x460, 0xc00 },
	{ 0x461, 0x8000 },
	{ 0x462, 0xc01 },
	{ 0x463, 0x50f0 },
	{ 0x464, 0xc01 },
	{ 0x465, 0x4820 },
	{ 0x466, 0xc01 },
	{ 0x466, 0xc01 },
	{ 0x467, 0x4040 },
	{ 0x468, 0xc01 },
	{ 0x468, 0xc01 },
	{ 0x469, 0x3940 },

Annotation

Immediate include surface: `linux/module.h`, `linux/mfd/arizona/core.h`, `linux/mfd/arizona/registers.h`, `linux/device.h`, `arizona.h`.
Detected declarations: `function wm5110_patch`, `function wm5110_is_rev_b_adsp_memory`, `function wm5110_is_rev_d_adsp_memory`, `function wm5110_is_adsp_memory`, `function wm5110_readable_register`, `function wm5110_volatile_register`, `export wm5110_patch`, `export wm5110_aod`, `export wm5110_irq`, `export wm5110_revd_irq`.
Atlas domain: Driver Families / drivers/mfd.
Implementation status: integration 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.