drivers/firewire/core-transaction.c

File Facts

System

Linux kernel

Corpus path

drivers/firewire/core-transaction.c

Extension

.c

Size

45624 bytes

Lines

1509

Domain

Driver Families

Bucket

drivers/firewire

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.
• 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/bug.h
• linux/completion.h
• linux/device.h
• linux/errno.h
• linux/firewire.h
• linux/firewire-constants.h
• linux/fs.h
• linux/init.h
• linux/jiffies.h
• linux/kernel.h
• linux/list.h
• linux/module.h
• linux/rculist.h
• linux/slab.h
• linux/spinlock.h
• linux/string.h
• linux/timer.h
• linux/types.h
• linux/workqueue.h
• asm/byteorder.h
• core.h
• packet-header-definitions.h
• phy-packet-definitions.h
• trace/events/firewire.h

Detected Declarations

• struct transaction_callback_data
• struct fw_request
• function Copyright
• function remove_transaction_entry
• function fw_cancel_pending_transactions
• function list_for_each_entry_safe
• function list_for_each_entry_safe
• function close_transaction
• function pending
• function split_transaction_timeout_callback
• function scoped_guard
• function start_split_transaction_timeout
• function transmit_complete_callback
• function scoped_guard
• function fw_fill_request
• function allocate_tlabel
• function __fw_send_request
• function transaction_callback
• function fw_run_transaction
• function transmit_phy_packet_callback
• function fw_send_phy_config
• function list_for_each_entry_rcu
• function is_enclosing_handler
• function list_for_each_entry_rcu
• function complete_address_handler
• function get_address_handler
• function put_address_handler
• function fw_core_add_address_handler
• function fw_core_remove_address_handler
• function fw_request_get
• function release_request
• function fw_request_put
• function free_response_callback
• function fw_get_response_length
• function fw_fill_response
• function compute_split_timeout_timestamp
• function fw_send_response
• function HEADER_DESTINATION_IS_BROADCAST
• function fw_get_request_speed
• function fw_request_get_timestamp
• function handle_exclusive_region_request
• function scoped_guard
• function handle_fcp_region_request
• function list_for_each_entry_rcu
• function fw_core_handle_request
• function fw_core_handle_response
• function handle_topology_map
• function update_split_timeout

Annotated Snippet

module_init(fw_core_init);
module_exit(fw_core_cleanup);

Annotation

• Immediate include surface: `linux/bug.h`, `linux/completion.h`, `linux/device.h`, `linux/errno.h`, `linux/firewire.h`, `linux/firewire-constants.h`, `linux/fs.h`, `linux/init.h`.
• Detected declarations: `struct transaction_callback_data`, `struct fw_request`, `function Copyright`, `function remove_transaction_entry`, `function fw_cancel_pending_transactions`, `function list_for_each_entry_safe`, `function list_for_each_entry_safe`, `function close_transaction`, `function pending`, `function split_transaction_timeout_callback`.
• Atlas domain: Driver Families / drivers/firewire.
• Implementation status: integration implementation candidate.

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.