drivers/soc/tegra/cbb/tegra194-cbb.c

File Facts

System

Linux kernel

Corpus path

drivers/soc/tegra/cbb/tegra194-cbb.c

Extension

.c

Size

96697 bytes

Lines

2355

Domain

Driver Families

Bucket

drivers/soc

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk.h
• linux/cpufeature.h
• linux/debugfs.h
• linux/module.h
• linux/of.h
• linux/of_address.h
• linux/platform_device.h
• linux/device.h
• linux/io.h
• linux/interrupt.h
• linux/ioport.h
• soc/tegra/fuse.h
• soc/tegra/tegra-cbb.h

Detected Declarations

• struct tegra194_cbb_packet_header
• struct tegra194_cbb_aperture
• struct tegra194_cbb_userbits
• struct tegra194_cbb_noc_data
• struct tegra194_axi2apb_bridge
• struct tegra194_cbb
• function cbbcentralnoc_parse_routeid
• function bpmpnoc_parse_routeid
• function aonnoc_parse_routeid
• function scenoc_parse_routeid
• function cbbcentralnoc_parse_userbits
• function clusternoc_parse_userbits
• function tegra194_cbb_fault_enable
• function tegra194_cbb_stall_enable
• function tegra194_cbb_error_clear
• function tegra194_cbb_get_status
• function tegra194_axi2apb_status
• function tegra194_axi2apb_fatal
• function get_init_localaddress
• function print_errlog5
• function print_errlog3_4
• function print_errlog1_2
• function print_errlog0
• function print_errloggerX_info
• function print_errlog
• function tegra194_cbb_debugfs_show
• function list_for_each_entry
• function tegra194_cbb_err_isr
• function CCPLEX
• function tegra194_cbb_interrupt_enable
• function tegra194_cbb_error_enable
• function tegra194_cbb_get_bridges
• function list_for_each_entry
• function tegra194_cbb_probe
• function tegra194_cbb_remove
• function list_for_each_entry_safe
• function tegra194_cbb_resume_noirq
• function tegra194_cbb_init
• function tegra194_cbb_exit
• module init tegra194_cbb_init

Annotated Snippet

core_initcall(tegra194_cbb_init);

static void __exit tegra194_cbb_exit(void)
{
	platform_driver_unregister(&tegra194_cbb_driver);
}
module_exit(tegra194_cbb_exit);

MODULE_AUTHOR("Sumit Gupta <sumitg@nvidia.com>");
MODULE_DESCRIPTION("Control Backbone error handling driver for Tegra194");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/cpufeature.h`, `linux/debugfs.h`, `linux/module.h`, `linux/of.h`, `linux/of_address.h`, `linux/platform_device.h`, `linux/device.h`.
• Detected declarations: `struct tegra194_cbb_packet_header`, `struct tegra194_cbb_aperture`, `struct tegra194_cbb_userbits`, `struct tegra194_cbb_noc_data`, `struct tegra194_axi2apb_bridge`, `struct tegra194_cbb`, `function cbbcentralnoc_parse_routeid`, `function bpmpnoc_parse_routeid`, `function aonnoc_parse_routeid`, `function scenoc_parse_routeid`.
• Atlas domain: Driver Families / drivers/soc.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.