drivers/platform/x86/fujitsu-tablet.c

File Facts

System

Linux kernel

Corpus path

drivers/platform/x86/fujitsu-tablet.c

Extension

.c

Size

11573 bytes

Lines

544

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/init.h
• linux/bitops.h
• linux/io.h
• linux/ioport.h
• linux/acpi.h
• linux/device.h
• linux/interrupt.h
• linux/input.h
• linux/delay.h
• linux/dmi.h
• linux/platform_device.h

Detected Declarations

• struct fujitsu_config
• function fujitsu_ack
• function fujitsu_status
• function fujitsu_read_register
• function fujitsu_send_state
• function fujitsu_reset
• function input_fujitsu_setup
• function input_fujitsu_remove
• function fujitsu_interrupt
• function for_each_set_bit
• function fujitsu_dmi_common
• function fujitsu_dmi_lifebook
• function fujitsu_dmi_stylistic
• function fujitsu_walk_resources
• function acpi_fujitsu_probe
• function acpi_fujitsu_remove
• function acpi_fujitsu_resume
• function fujitsu_module_init
• function fujitsu_module_exit
• module init fujitsu_module_init

Annotated Snippet

module_init(fujitsu_module_init);
module_exit(fujitsu_module_exit);

MODULE_AUTHOR("Robert Gerlach <khnz@gmx.de>");
MODULE_DESCRIPTION("Fujitsu tablet pc extras driver");
MODULE_LICENSE("GPL");
MODULE_VERSION("2.5");

MODULE_DEVICE_TABLE(acpi, fujitsu_ids);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `linux/bitops.h`, `linux/io.h`, `linux/ioport.h`, `linux/acpi.h`, `linux/device.h`.
• Detected declarations: `struct fujitsu_config`, `function fujitsu_ack`, `function fujitsu_status`, `function fujitsu_read_register`, `function fujitsu_send_state`, `function fujitsu_reset`, `function input_fujitsu_setup`, `function input_fujitsu_remove`, `function fujitsu_interrupt`, `function for_each_set_bit`.
• Atlas domain: Driver Families / drivers/platform.
• Implementation status: integration implementation candidate.
• 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.