drivers/net/can/cc770/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/can/cc770/Kconfig
Extension: [no extension]
Size: 646 bytes
Lines: 24
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
menuconfig CAN_CC770
	tristate "Bosch CC770 and Intel AN82527 devices"
	depends on HAS_IOMEM

if CAN_CC770

config CAN_CC770_ISA
	tristate "ISA Bus based legacy CC770 driver"
	depends on HAS_IOPORT
	help
	  This driver adds legacy support for CC770 and AN82527 chips
	  connected to the ISA bus using I/O port, memory mapped or
	  indirect access.

config CAN_CC770_PLATFORM
	tristate "Generic Platform Bus based CC770 driver"
	help
	  This driver adds support for the CC770 and AN82527 chips
	  connected to the "platform bus" (Linux abstraction for directly
	  to the processor attached devices).

endif

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.