drivers/mfd/ocelot.h

File Facts

System

Linux kernel

Corpus path

drivers/mfd/ocelot.h

Extension

.h

Size

1459 bytes

Lines

50

Domain

Driver Families

Bucket

drivers/mfd

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/kconfig.h

Detected Declarations

• struct device
• struct regmap
• struct resource
• struct ocelot_ddata

Annotated Snippet

struct ocelot_ddata {
	struct regmap *gcb_regmap;
	struct regmap *cpuorg_regmap;
	int spi_padding_bytes;
	void *dummy_buf;
};

int ocelot_chip_reset(struct device *dev);
int ocelot_core_init(struct device *dev);

/* SPI-specific routines that won't be necessary for other interfaces */
struct regmap *ocelot_spi_init_regmap(struct device *dev,
				      const struct resource *res);

#define OCELOT_SPI_BYTE_ORDER_LE 0x00000000
#define OCELOT_SPI_BYTE_ORDER_BE 0x81818181

#ifdef __LITTLE_ENDIAN
#define OCELOT_SPI_BYTE_ORDER OCELOT_SPI_BYTE_ORDER_LE
#else
#define OCELOT_SPI_BYTE_ORDER OCELOT_SPI_BYTE_ORDER_BE
#endif

#endif

Annotation

• Immediate include surface: `linux/kconfig.h`.
• Detected declarations: `struct device`, `struct regmap`, `struct resource`, `struct ocelot_ddata`.
• Atlas domain: Driver Families / drivers/mfd.
• 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.