drivers/fpga/lattice-sysconfig.h

File Facts

System

Linux kernel

Corpus path

drivers/fpga/lattice-sysconfig.h

Extension

.h

Size

1430 bytes

Lines

40

Domain

Driver Families

Bucket

drivers/fpga

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

• struct sysconfig_priv

Annotated Snippet

struct sysconfig_priv {
	struct gpio_desc *program;
	struct gpio_desc *init;
	struct gpio_desc *done;
	struct device *dev;
	int (*command_transfer)(struct sysconfig_priv *priv, const void *tx_buf,
				size_t tx_len, void *rx_buf, size_t rx_len);
	int (*bitstream_burst_write_init)(struct sysconfig_priv *priv);
	int (*bitstream_burst_write)(struct sysconfig_priv *priv,
				     const char *tx_buf, size_t tx_len);
	int (*bitstream_burst_write_complete)(struct sysconfig_priv *priv);
};

int sysconfig_probe(struct sysconfig_priv *priv);

#endif /* __LATTICE_SYSCONFIG_H */

Annotation

• Detected declarations: `struct sysconfig_priv`.
• Atlas domain: Driver Families / drivers/fpga.
• 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.