Keyboard-driver lifecycle reference
A reference to keyboard identity, reports, class behavior, and the layers that carry key events.
Key events begin as reports
A keyboard interface reports state changes through a transport-specific format. The report can contain keys, modifiers, LEDs, or other controls, while the host input stack turns those fields into a logical keyboard representation. The physical keys and the host events are related but not the same object.
Class behavior and vendor features
Standard keyboard behavior is often represented through shared input conventions. A vendor can also expose extra keys, lighting, macros, or configuration through separate interfaces or services. Those optional features should not be assumed to be part of the basic keyboard class contract.
Lifecycle boundaries
Enumeration, matching, package selection, activation, and input delivery describe different points in a keyboard’s software lifecycle. A transport driver can carry reports, a class component can interpret them, and a user-mode service can add policy or configuration without replacing the input contract.
Version and identity clues
Keyboard package records may use hardware identifiers, interface identifiers, transport names, or service names. Reading a version requires knowing which record owns it. Friendly names are useful for navigation, but they are not a complete description of the device stack.
Reference facts
- Input contract
- Reports are translated into logical key and control events
- Optional layers
- Vendor services may expose controls beyond standard input behavior
- Identity
- Transport, interface, class, and service records can differ
Questions and answers
Is a keyboard driver a map of letters to characters?
Not by itself. The driver and input stack carry device reports and key identities; layout and text composition are higher-level concerns.
Can a keyboard expose more than one interface?
Yes. A physical keyboard can present standard input along with optional control or configuration interfaces.
Why do keyboard and laptop keyboard records differ?
An internal keyboard can use an embedded controller or platform-specific interface, while an external keyboard commonly presents a standard transport and input interface.