drivers/platform/x86/meraki-mx100.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/meraki-mx100.c

Extension

.c

Size

9764 bytes

Lines

351

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/dmi.h
• linux/err.h
• linux/gpio/machine.h
• linux/gpio/property.h
• linux/input-event-codes.h
• linux/io.h
• linux/kernel.h
• linux/module.h
• linux/platform_device.h
• linux/property.h

Detected Declarations

• function tink_board_init
• function tink_board_exit
• module init tink_board_init

Annotated Snippet

module_init(tink_board_init);

static void __exit tink_board_exit(void)
{
	platform_device_unregister(tink_keys_pdev);
	platform_device_unregister(tink_leds_pdev);
	software_node_unregister_node_group(tink_swnodes);
}
module_exit(tink_board_exit);

MODULE_AUTHOR("Chris Blake <chrisrblake93@gmail.com>");
MODULE_DESCRIPTION("Cisco Meraki MX100 Platform Driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:meraki-mx100");

Annotation

• Immediate include surface: `linux/dmi.h`, `linux/err.h`, `linux/gpio/machine.h`, `linux/gpio/property.h`, `linux/input-event-codes.h`, `linux/io.h`, `linux/kernel.h`, `linux/module.h`.
• Detected declarations: `function tink_board_init`, `function tink_board_exit`, `module init tink_board_init`.
• Atlas domain: Driver Families / drivers/platform.
• 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.