-
Notifications
You must be signed in to change notification settings - Fork 3k
Runtime Mode change of PIN #7334
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
Comments
ARM Internal Ref: MBOTRIAGE-928 |
This is not yet defined, but should be. This will be address by the specs update for all HAL (including those you are using). ctor initializes it for specific functionality, but not all drivers call free (so dtor is empty). Therefore the state is preserved. The answer would be, state changes only on initialization. @ARMmbed/mbed-os-core Please review |
It would be greate if there would be a |
This is duplicate of #3106. Since destructor code is empty, deallocation is not done. |
Description
I have a set of pins which are re=used depending on the operation mode (SPI, I2C, GPIO IRQ, ADC, DigitalOut).
What is the desired way of doing this in mbed os?
If I utilize a PIN as
DigitalOut
, which de-allocates with a scope and afterwards allocate again withDigitalIn
.What is the state while it is not allocated? Is it going back to the default state (and where is that defined?)
Issue request type
[X] Question
[ ] Enhancement
[ ] Bug
The text was updated successfully, but these errors were encountered: