This repository has been archived by the owner on Aug 5, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 64
[GPIOPins] Fail to close GPIOPins #311
Comments
Technically, it doesn't say that won't work. It says you shouldn't do that. (I.e. it might not work in the future.) But yeah, probably we should force it to not work so people don't rely on this behavior. |
So, I think it is better method of forcing it to not work. |
FWIW I see onchange does get disabled, but you're right, read/write don't. |
grgustaf
added a commit
to grgustaf/zephyr.js-1
that referenced
this issue
Dec 23, 2016
Fixes issue intel#311. Signed-off-by: Geoff Gustafson <[email protected]>
grgustaf
added a commit
to grgustaf/zephyr.js-1
that referenced
this issue
Dec 23, 2016
Fixes issue intel#311. Signed-off-by: Geoff Gustafson <[email protected]>
This should be fixed by #577. |
grgustaf
added a commit
that referenced
this issue
Dec 28, 2016
Fixes issue #311. Signed-off-by: Geoff Gustafson <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After closed the GPIO pin, I can read and write this pin. It is different to description of GPIOPin.close function.
GPIOPin.close
void close();
Free up resources associated with the pin. The onchange function for this pin will no longer be called, and the object should not be used for reading and writing anymore.
The text was updated successfully, but these errors were encountered: