drivers/hid/hid-playstation.c

File Facts

System

Linux kernel

Corpus path

drivers/hid/hid-playstation.c

Extension

.c

Size

94073 bytes

Lines

2991

Domain

Driver Families

Bucket

drivers/hid

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/bitfield.h
• linux/bits.h
• linux/cleanup.h
• linux/crc32.h
• linux/device.h
• linux/hid.h
• linux/idr.h
• linux/input/mt.h
• linux/leds.h
• linux/led-class-multicolor.h
• linux/module.h
• linux/unaligned.h
• hid-ids.h

Detected Declarations

• struct ps_device
• struct ps_calibration_data
• struct ps_led_info
• struct dualsense
• struct dualsense_touch_point
• struct dualsense_input_report
• struct dualsense_output_report_common
• struct dualsense_output_report_bt
• struct dualsense_output_report_usb
• struct dualsense_output_report
• struct dualshock4
• struct dualshock4_touch_point
• struct dualshock4_touch_report
• struct dualshock4_input_report_common
• struct dualshock4_input_report_usb
• struct dualshock4_input_report_bt
• struct dualshock4_output_report_common
• struct dualshock4_output_report_usb
• struct dualshock4_output_report_bt
• struct dualshock4_output_report
• enum PS_TYPE
• enum dualshock4_dongle_state
• function ps_devices_list_add
• function list_for_each_entry
• function ps_devices_list_remove
• function ps_device_set_player_id
• function ps_device_release_player_id
• function ps_battery_get_property
• function scoped_guard
• function ps_device_register_battery
• function ps_check_crc32
• function ps_gamepad_create
• function ps_get_report
• function ps_led_register
• function ps_lightbar_register
• function firmware_version_show
• function hardware_version_show
• function dualsense_get_calibration_data
• function dualsense_get_firmware_info
• function dualsense_get_mac_address
• function dualsense_lightbar_set_brightness
• function dualsense_player_led_get_brightness
• function dualsense_player_led_set_brightness
• function scoped_guard
• function dualsense_init_output_report
• function dualsense_schedule_work
• function dualsense_send_output_report
• function dualsense_output_worker

Annotated Snippet

module_init(ps_init);
module_exit(ps_exit);

MODULE_AUTHOR("Sony Interactive Entertainment");
MODULE_DESCRIPTION("HID Driver for PlayStation peripherals.");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/bitfield.h`, `linux/bits.h`, `linux/cleanup.h`, `linux/crc32.h`, `linux/device.h`, `linux/hid.h`, `linux/idr.h`, `linux/input/mt.h`.
• Detected declarations: `struct ps_device`, `struct ps_calibration_data`, `struct ps_led_info`, `struct dualsense`, `struct dualsense_touch_point`, `struct dualsense_input_report`, `struct dualsense_output_report_common`, `struct dualsense_output_report_bt`, `struct dualsense_output_report_usb`, `struct dualsense_output_report`.
• Atlas domain: Driver Families / drivers/hid.
• 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.