drivers/net/can/rcar/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/net/can/rcar/Kconfig
Extension: [no extension]
Size: 767 bytes
Lines: 23
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
config CAN_RCAR
	tristate "Renesas R-Car and RZ/G CAN controller"
	depends on ARCH_RENESAS || COMPILE_TEST
	help
	  Say Y here if you want to use CAN controller found on Renesas R-Car
	  or RZ/G SoCs.

	  To compile this driver as a module, choose M here: the module will
	  be called rcar_can.

config CAN_RCAR_CANFD
	tristate "Renesas R-Car CAN FD controller"
	depends on ARCH_RENESAS || COMPILE_TEST
	help
	  Say Y here if you want to use CAN FD controller found on
	  Renesas R-Car SoCs. The driver puts the controller in CAN FD only
	  mode, which can interoperate with CAN2.0 nodes but does not support
	  dedicated CAN 2.0 mode.

	  To compile this driver as a module, choose M here: the module will
	  be called rcar_canfd.

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.