| Previous | Next |
| STATUS_SECONDARY_IC_PROVIDER_NOT_REGISTERED | STATUS_GPIO_VERSION_NOT_SUPPORTED |
STATUS_GPIO_CLIENT_INFORMATION_INVALID
GpioClx rejected the controller driver description
A GPIO controller driver registers with the GPIO framework extension and supplies information describing its callbacks and controller behavior. This status indicates that the client information fails validation before normal pin I/O can proceed. It is a driver-contract problem, not a failure of a particular electrical input value.
The registration packet and controller-information callback must agree about supported operations, bank layout, interrupt handling, and callback variants. Structure initialization bugs, incorrect size or version fields, and callbacks inconsistent with advertised capabilities are common areas to inspect.
What to inspect
- Capture the registration packet, structure sizes and versions, callback pointers, and controller basic information.
- Compare initialization with the current GpioClx header and Microsoft sample driver.
- Verify required callbacks are non-null and optional callback choices match advertised controller capabilities.
- Check for packing, lifetime, or memory corruption before the GPIO_CLX_RegisterClient call.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: GpioClx DDI
- Microsoft: GPIO_CLIENT_REGISTRATION_PACKET
- Microsoft driver samples: GPIO controllers and clients
Looking for a different code? Search another status or error code.