drivers/net/ethernet/wiznet/w5100.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/wiznet/w5100.h

Extension

.h

Size

1008 bytes

Lines

36

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct w5100_ops

Annotated Snippet

struct w5100_ops {
	bool may_sleep;
	int chip_id;
	int (*read)(struct net_device *ndev, u32 addr);
	int (*write)(struct net_device *ndev, u32 addr, u8 data);
	int (*read16)(struct net_device *ndev, u32 addr);
	int (*write16)(struct net_device *ndev, u32 addr, u16 data);
	int (*readbulk)(struct net_device *ndev, u32 addr, u8 *buf, int len);
	int (*writebulk)(struct net_device *ndev, u32 addr, const u8 *buf,
			 int len);
	int (*reset)(struct net_device *ndev);
	int (*init)(struct net_device *ndev);
};

void *w5100_ops_priv(const struct net_device *ndev);

int w5100_probe(struct device *dev, const struct w5100_ops *ops,
		int sizeof_ops_priv, const void *mac_addr, int irq);
void w5100_remove(struct device *dev);

extern const struct dev_pm_ops w5100_pm_ops;

Annotation

• Detected declarations: `struct w5100_ops`.
• 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.