Driver Completeness
Completion boundary
SLeeLa distinguishes shared driver infrastructure from device-specific completeness.
Shared infrastructure
The common driver layer provides:
- hardware profile metadata;
- pin, voltage and memory abstractions;
- cache/DMA policy;
- bounded data-plane queues;
- frame sequencing and timestamps;
- CRC-32 integrity checking;
- producer/consumer synchronization;
- mutex and condition-variable locking;
- blocking/timed receive;
- backpressure;
- start/stop/destroy lifecycle;
- platform transport boundaries.
Device-specific completion
A concrete driver must additionally account for the applicable:
- exact model and hardware revision;
- firmware/interface version where discoverable;
- transport;
- USB/Bluetooth/network/audio/HID descriptors;
- pin and control mappings when hardware-level control is exposed;
- register or memory mappings when applicable;
- HID report layouts and usages when applicable;
- command and response paths;
- input/output data paths;
- state transitions;
- error and recovery paths;
- hotplug/reconnect behavior;
- cache/DMA requirements;
- unsupported-feature reporting;
- platform-specific behavior;
- test evidence.
Audit status
The absence of TODO/STUB/ENOSYS markers is not, by itself, proof of completeness.
Use these status concepts:
- Generic implementation — reusable behavior that does not claim every model-specific detail.
- Provisional path — an implementation operating behind an explicit evidence boundary.
- Verified path — a path supported by documented, enumerated, measured or tested evidence.
- Hardware-operational — required device-specific operations are implemented for the documented scope.
- Hardware-complete — the applicable control, data, state, error, recovery, synchronization and hardware-mapping paths have been audited and remaining gaps are explicitly recorded.
Never convert an assumption into an actual hardware value merely to make a driver appear complete.