drivers/firewire/sbp2.c

File Facts

System

Linux kernel

Corpus path

drivers/firewire/sbp2.c

Extension

.c

Size

46970 bytes

Lines

1624

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.
• 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/blkdev.h
• linux/bug.h
• linux/completion.h
• linux/delay.h
• linux/device.h
• linux/dma-mapping.h
• linux/firewire.h
• linux/firewire-constants.h
• linux/init.h
• linux/jiffies.h
• linux/kernel.h
• linux/kref.h
• linux/list.h
• linux/mod_devicetable.h
• linux/module.h
• linux/moduleparam.h
• linux/scatterlist.h
• linux/slab.h
• linux/spinlock.h
• linux/string.h
• linux/stringify.h
• linux/workqueue.h
• asm/byteorder.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi_host.h

Detected Declarations

• struct sbp2_logical_unit
• struct sbp2_target
• struct sbp2_status
• struct sbp2_pointer
• struct sbp2_orb
• struct sbp2_management_orb
• struct sbp2_login_response
• struct sbp2_command_orb
• function sbp2_queue_work
• function free_orb
• function sbp2_status_write
• function complete_transaction
• function sbp2_send_orb
• function sbp2_cancel_orbs
• function list_for_each_entry_safe
• function complete_management_orb
• function sbp2_send_management_orb
• function sbp2_agent_reset
• function complete_agent_reset_write_no_wait
• function sbp2_agent_reset_no_wait
• function sbp2_allow_block
• function finished
• function sbp2_conditionally_unblock
• function sbp2_unblock
• function sbp2_lun2int
• function sbp2_set_busy_timeout
• function sbp2_login
• function sbp2_reconnect
• function sbp2_lu_workfn
• function sbp2_add_logical_unit
• function sbp2_get_unit_unique_id
• function sbp2_scan_logical_unit_dir
• function sbp2_scan_unit_dir
• function sbp2_clamp_management_orb_timeout
• function sbp2_init_workarounds
• function sbp2_probe
• function sbp2_update
• function sbp2_remove
• function list_for_each_entry_safe
• function sbp2_unmap_scatterlist
• function sbp2_status_to_sense_data
• function complete_command_orb
• function sbp2_map_scatterlist
• function for_each_sg
• function sbp2_scsi_queuecommand
• function sbp2_scsi_sdev_init
• function sbp2_scsi_sdev_configure
• function sbp2_scsi_abort

Annotated Snippet

module_init(sbp2_init);
module_exit(sbp2_cleanup);

Annotation

• Immediate include surface: `linux/blkdev.h`, `linux/bug.h`, `linux/completion.h`, `linux/delay.h`, `linux/device.h`, `linux/dma-mapping.h`, `linux/firewire.h`, `linux/firewire-constants.h`.
• Detected declarations: `struct sbp2_logical_unit`, `struct sbp2_target`, `struct sbp2_status`, `struct sbp2_pointer`, `struct sbp2_orb`, `struct sbp2_management_orb`, `struct sbp2_login_response`, `struct sbp2_command_orb`, `function sbp2_queue_work`, `function free_orb`.
• Atlas domain: Driver Families / drivers/firewire.
• 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.