drivers/net/can/softing/softing_platform.h

File Facts

System

Linux kernel

Corpus path

drivers/net/can/softing/softing_platform.h

Extension

.h

Size

909 bytes

Lines

42

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

• linux/platform_device.h

Detected Declarations

• struct softing_platform_data

Annotated Snippet

struct softing_platform_data {
	unsigned int manf;
	unsigned int prod;
	/*
	 * generation
	 * 1st with NEC or SJA1000
	 * 8bit, exclusive interrupt, ...
	 * 2nd only SJA1000
	 * 16bit, shared interrupt
	 */
	int generation;
	int nbus; /* # buses on device */
	unsigned int freq; /* operating frequency in Hz */
	unsigned int max_brp;
	unsigned int max_sjw;
	unsigned long dpram_size;
	const char *name;
	struct {
		unsigned long offs;
		unsigned long addr;
		const char *fw;
	} boot, load, app;
	/*
	 * reset() function
	 * bring pdev in or out of reset, depending on value
	 */
	int (*reset)(struct platform_device *pdev, int value);
	int (*enable_irq)(struct platform_device *pdev, int value);
};

#endif

Annotation

• Immediate include surface: `linux/platform_device.h`.
• Detected declarations: `struct softing_platform_data`.
• 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.