-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can gpio in lgGpioReport_t be changed to uint16_t? #30
Comments
I will have to find some time to look into this. I thought that gpiochip GPIO numbers were constarined to be 0-63. lg is a very low priority for me - don't expect a response soon. |
I understand. I forked, changed it to uint16, and it works fine so far. I'll use that in the meantime. Opened a PR for the change as well. |
GPIO numbers (i.e. offsets) are NOT constrained to 0-63. You are probably thinking of the number of lines in a request which is limited to 64, cos who would want to request more than 64 lines at once, but individual GPIO chips can and do exceed that so offsets can be larger. |
Updated my PR to 32 bits. |
I'm using an Orange Pi Zero 2W. For whatever reason, the GPIO numbers on this exceed 255, so when using
lgGpioSetSamplesFunc
, I get reports where the GPIO numbers overflow. Reports from GPIO 258 appear to be coming from GPIO 2 for example.The text was updated successfully, but these errors were encountered: