drivers/net/can/spi/mcp251xfd/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/can/spi/mcp251xfd/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/can/spi/mcp251xfd/Kconfig
Extension: [no extension]
Size: 559 bytes
Lines: 21
Domain: Driver Families
Bucket: drivers/net
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

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.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only

config CAN_MCP251XFD
	tristate "Microchip MCP251xFD SPI CAN controllers"
	select CAN_RX_OFFLOAD
	select REGMAP
	select WANT_DEV_COREDUMP
	select GPIOLIB
	help
	  Driver for the Microchip MCP251XFD SPI FD-CAN controller
	  family.

config CAN_MCP251XFD_SANITY
	depends on CAN_MCP251XFD
	bool "Additional Sanity Checks"
	help
	  This option enables additional sanity checks in the driver,
	  that compares various internal counters with the in chip
	  variants. This comes with a runtime overhead.
	  Disable if unsure.

Annotation

Atlas domain: Driver Families / drivers/net.
Implementation status: atlas-only.

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.