drivers/spi/spi-loongson.h

File Facts

System

Linux kernel

Corpus path

drivers/spi/spi-loongson.h

Extension

.h

Size

1344 bytes

Lines

50

Domain

Driver Families

Bucket

drivers/spi

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/bits.h
• linux/pm.h
• linux/types.h

Detected Declarations

• struct device
• struct spi_controller
• struct loongson_spi

Annotated Snippet

struct loongson_spi {
	struct	spi_controller	*controller;
	void __iomem		*base;
	int			cs_active;
	unsigned int		hz;
	unsigned char		spcr;
	unsigned char		sper;
	unsigned char		spsr;
	unsigned char		para;
	unsigned char		sfcs;
	unsigned char		timi;
	unsigned int		mode;
	u64			clk_rate;
};

int loongson_spi_init_controller(struct device *dev, void __iomem *reg);
extern const struct dev_pm_ops loongson_spi_dev_pm_ops;
#endif /* __LINUX_SPI_LOONGSON_H */

Annotation

• Immediate include surface: `linux/bits.h`, `linux/pm.h`, `linux/types.h`.
• Detected declarations: `struct device`, `struct spi_controller`, `struct loongson_spi`.
• Atlas domain: Driver Families / drivers/spi.
• 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.