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

File Facts

System

Linux kernel

Corpus path

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

Extension

.c

Size

51820 bytes

Lines

1786

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/acpi.h
• linux/clk.h
• linux/cpufeature.h
• linux/debugfs.h
• linux/module.h
• linux/of.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 tegra234_target_lookup
• struct tegra234_fabric_lookup
• struct tegra234_cbb_fabric
• struct tegra234_cbb
• struct tegra234_cbb_acpi_uid
• enum tegra234_cbb_fabric_ids
• enum tegra238_cbb_fabric_ids
• enum tegra264_cbb_fabric_ids
• enum t254_cbb_fabric_ids
• function tegra234_cbb_write_access_allowed
• function tegra234_cbb_fault_enable
• function tegra234_cbb_error_clear
• function tegra234_cbb_get_status
• function tegra234_cbb_mask_serror
• function tegra234_cbb_get_tmo_slv
• function tegra234_cbb_tmo_slv
• function tegra234_cbb_lookup_apbslv
• function list_for_each_entry
• function tegra234_sw_lookup_target_timeout
• function tegra234_hw_lookup_target_timeout
• function tegra234_cbb_print_error
• function print_errlog_err
• function print_errmonX_info
• function print_err_notifier
• function tegra234_cbb_debugfs_show
• function list_for_each_entry
• function tegra234_cbb_isr
• function list_for_each_entry
• function CCPLEX
• function tegra234_cbb_interrupt_enable
• function tegra234_cbb_error_enable
• function tegra234_cbb_probe
• function tegra234_cbb_resume_noirq
• function tegra234_cbb_init
• function tegra234_cbb_exit
• module init tegra234_cbb_init

Annotated Snippet

core_initcall(tegra234_cbb_init);

static void __exit tegra234_cbb_exit(void)
{
	platform_driver_unregister(&tegra234_cbb_driver);
}
module_exit(tegra234_cbb_exit);

MODULE_DESCRIPTION("Control Backbone 2.0 error handling driver for Tegra234");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/clk.h`, `linux/cpufeature.h`, `linux/debugfs.h`, `linux/module.h`, `linux/of.h`, `linux/platform_device.h`, `linux/device.h`.
• Detected declarations: `struct tegra234_target_lookup`, `struct tegra234_fabric_lookup`, `struct tegra234_cbb_fabric`, `struct tegra234_cbb`, `struct tegra234_cbb_acpi_uid`, `enum tegra234_cbb_fabric_ids`, `enum tegra238_cbb_fabric_ids`, `enum tegra264_cbb_fabric_ids`, `enum t254_cbb_fabric_ids`, `function tegra234_cbb_write_access_allowed`.
• 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.