drivers/platform/surface/aggregator/core.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/surface/aggregator/core.c

Extension

.c

Size

24718 bytes

Lines

895

Domain

Driver Families

Bucket

drivers/platform

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.
• 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/atomic.h
• linux/completion.h
• linux/gpio/consumer.h
• linux/kernel.h
• linux/kref.h
• linux/module.h
• linux/of.h
• linux/platform_device.h
• linux/pm.h
• linux/serdev.h
• linux/sysfs.h
• linux/units.h
• linux/surface_aggregator/controller.h
• linux/surface_aggregator/device.h
• bus.h
• controller.h
• trace.h

Detected Declarations

• function ssam_get_controller
• function ssam_try_set_controller
• function ssam_clear_controller
• function ssam_client_link
• function ssam_client_bind
• function ssam_receive_buf
• function ssam_write_wakeup
• function ssam_log_firmware_version
• function firmware_version_show
• function ssam_serdev_setup_via_acpi_crs
• function ssam_serdev_setup_via_acpi
• function ssam_serdev_setup
• function ssam_serial_hub_shutdown
• function ssam_serial_hub_pm_prepare
• function ssam_serial_hub_pm_complete
• function ssam_serial_hub_pm_suspend
• function ssam_serial_hub_pm_resume
• function ssam_serial_hub_pm_freeze
• function ssam_serial_hub_pm_thaw
• function ssam_serial_hub_pm_poweroff
• function ssam_serial_hub_pm_restore
• function ssam_serial_hub_probe
• function ssam_serial_hub_remove
• function ssam_core_init
• function ssam_core_exit
• module init ssam_core_init
• export ssam_get_controller
• export ssam_client_link
• export ssam_client_bind

Annotated Snippet

subsys_initcall(ssam_core_init);

static void __exit ssam_core_exit(void)
{
	serdev_device_driver_unregister(&ssam_serial_hub);
	ssam_event_item_cache_destroy();
	ssh_ctrl_packet_cache_destroy();
	ssam_bus_unregister();
}
module_exit(ssam_core_exit);

MODULE_AUTHOR("Maximilian Luz <luzmaximilian@gmail.com>");
MODULE_DESCRIPTION("Subsystem and Surface Serial Hub driver for Surface System Aggregator Module");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/atomic.h`, `linux/completion.h`, `linux/gpio/consumer.h`, `linux/kernel.h`, `linux/kref.h`, `linux/module.h`, `linux/of.h`.
• Detected declarations: `function ssam_get_controller`, `function ssam_try_set_controller`, `function ssam_clear_controller`, `function ssam_client_link`, `function ssam_client_bind`, `function ssam_receive_buf`, `function ssam_write_wakeup`, `function ssam_log_firmware_version`, `function firmware_version_show`, `function ssam_serdev_setup_via_acpi_crs`.
• Atlas domain: Driver Families / drivers/platform.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.