drivers/hsi/controllers/omap_ssi_core.c

File Facts

System

Linux kernel

Corpus path

drivers/hsi/controllers/omap_ssi_core.c

Extension

.c

Size

17095 bytes

Lines

646

Domain

Driver Families

Bucket

drivers/hsi

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/compiler.h
• linux/err.h
• linux/ioport.h
• linux/io.h
• linux/clk.h
• linux/device.h
• linux/platform_device.h
• linux/dma-mapping.h
• linux/dmaengine.h
• linux/delay.h
• linux/hsi/ssi_protocol.h
• linux/seq_file.h
• linux/scatterlist.h
• linux/interrupt.h
• linux/spinlock.h
• linux/debugfs.h
• linux/pinctrl/consumer.h
• linux/pm_runtime.h
• linux/of.h
• linux/of_platform.h
• linux/hsi/hsi.h
• linux/idr.h
• omap_ssi_regs.h
• omap_ssi.h

Detected Declarations

• function ssi_regs_show
• function ssi_gdd_regs_show
• function ssi_debug_add_ctrl
• function ssi_debug_remove_ctrl
• function ssi_waketest
• function ssi_gdd_complete
• function ssi_gdd_tasklet
• function ssi_gdd_isr
• function ssi_get_clk_rate
• function ssi_clk_event
• function ssi_get_iomem
• function ssi_add_controller
• function ssi_hw_init
• function ssi_remove_controller
• function ssi_of_get_available_ports_count
• function ssi_remove_ports
• function ssi_probe
• function for_each_available_child_of_node
• function ssi_remove
• function omap_ssi_runtime_suspend
• function omap_ssi_runtime_resume
• function ssi_init
• function ssi_exit
• module init ssi_init
• export ssi_waketest

Annotated Snippet

module_init(ssi_init);

static void __exit ssi_exit(void) {
	platform_driver_unregister(&ssi_port_pdriver);
	platform_driver_unregister(&ssi_pdriver);
}
module_exit(ssi_exit);

MODULE_ALIAS("platform:omap_ssi");
MODULE_AUTHOR("Carlos Chinea <carlos.chinea@nokia.com>");
MODULE_AUTHOR("Sebastian Reichel <sre@kernel.org>");
MODULE_DESCRIPTION("Synchronous Serial Interface Driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/compiler.h`, `linux/err.h`, `linux/ioport.h`, `linux/io.h`, `linux/clk.h`, `linux/device.h`, `linux/platform_device.h`, `linux/dma-mapping.h`.
• Detected declarations: `function ssi_regs_show`, `function ssi_gdd_regs_show`, `function ssi_debug_add_ctrl`, `function ssi_debug_remove_ctrl`, `function ssi_waketest`, `function ssi_gdd_complete`, `function ssi_gdd_tasklet`, `function ssi_gdd_isr`, `function ssi_get_clk_rate`, `function ssi_clk_event`.
• Atlas domain: Driver Families / drivers/hsi.
• 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.