drivers/hwtracing/coresight/coresight-trbe.c

File Facts

System

Linux kernel

Corpus path

drivers/hwtracing/coresight/coresight-trbe.c

Extension

.c

Size

48676 bytes

Lines

1606

Domain

Driver Families

Bucket

drivers/hwtracing

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.
• 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

• asm/barrier.h
• asm/cpufeature.h
• linux/kvm_host.h
• linux/vmalloc.h
• coresight-self-hosted-trace.h
• coresight-trbe.h

Detected Declarations

• struct trbe_buf
• struct trbe_cpudata
• struct trbe_drvdata
• enum trbe_fault_action
• function trbe_check_errata
• function trbe_has_erratum
• function trbe_may_overwrite_in_fill_mode
• function trbe_may_write_out_of_range
• function trbe_needs_drain_after_disable
• function trbe_needs_ctxt_sync_after_enable
• function trbe_is_broken
• function trbe_alloc_node
• function trbe_drain_buffer
• function set_trbe_enabled
• function set_trbe_disabled
• function trbe_drain_and_disable_local
• function trbe_reset_local
• function trbe_report_wrap_event
• function trbe_stop_and_truncate_event
• function indices
• function trbe_pad_buf
• function trbe_snapshot_offset
• function trbe_min_trace_buf_size
• function __trbe_normal_offset
• function trbe_normal_offset
• function compute_trbe_buffer_limit
• function clr_trbe_status
• function set_trbe_limit_pointer_enabled
• function trbe_enable_hw
• function trbe_get_fault_act
• function trbe_get_trace_size
• function arm_trbe_free_buffer
• function arm_trbe_update_buffer
• function trbe_apply_work_around_before_enable
• function entity
• function __arm_trbe_enable
• function arm_trbe_enable
• function arm_trbe_disable
• function trbe_handle_spurious
• function trbe_handle_overflow
• function is_perf_trbe
• function cpu_prohibit_trace
• function arm_trbe_irq_handler
• function align_show
• function flag_show
• function arm_trbe_enable_cpu
• function arm_trbe_disable_cpu
• function arm_trbe_register_coresight_cpu

Annotated Snippet

module_init(arm_trbe_init);
module_exit(arm_trbe_exit);

MODULE_AUTHOR("Anshuman Khandual <anshuman.khandual@arm.com>");
MODULE_DESCRIPTION("Arm Trace Buffer Extension (TRBE) driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `asm/barrier.h`, `asm/cpufeature.h`, `linux/kvm_host.h`, `linux/vmalloc.h`, `coresight-self-hosted-trace.h`, `coresight-trbe.h`.
• Detected declarations: `struct trbe_buf`, `struct trbe_cpudata`, `struct trbe_drvdata`, `enum trbe_fault_action`, `function trbe_check_errata`, `function trbe_has_erratum`, `function trbe_may_overwrite_in_fill_mode`, `function trbe_may_write_out_of_range`, `function trbe_needs_drain_after_disable`, `function trbe_needs_ctxt_sync_after_enable`.
• Atlas domain: Driver Families / drivers/hwtracing.
• Implementation status: integration implementation candidate.
• 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.