drivers/firmware/tegra/Kconfig

Source file repositories/reference/linux-study-clean/drivers/firmware/tegra/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/firmware/tegra/Kconfig
Extension: [no extension]
Size: 919 bytes
Lines: 29
Domain: Driver Families
Bucket: drivers/firmware
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
menu "Tegra firmware driver"

config TEGRA_IVC
	bool
	depends on ARCH_TEGRA
	help
	  IVC (Inter-VM Communication) protocol is part of the IPC
	  (Inter Processor Communication) framework on Tegra. It maintains the
	  data and the different communication channels in SysRAM or RAM and
	  keeps the content is synchronization between host CPU and remote
	  processors.

config TEGRA_BPMP
	bool "Tegra BPMP driver"
	depends on ARCH_TEGRA && TEGRA_HSP_MBOX
	depends on !CPU_BIG_ENDIAN
	select TEGRA_IVC
	help
	  BPMP (Boot and Power Management Processor) is designed to off-loading
	  the PM functions which include clock/DVFS/thermal/power from the CPU.
	  It needs HSP as the HW synchronization and notification module and
	  IVC module as the message communication protocol.

	  This driver manages the IPC interface between host CPU and the
	  firmware running on BPMP.

endmenu

Annotation

Atlas domain: Driver Families / drivers/firmware.
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.