You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may not need a separate OutputOpenDrain driver. In fact, for future proofing reasons, we might want to prefer encoding the output mode in the associated configuration.
We might want to omit the initial level from the associated configuration, and just pass it to the constructor. Setting the initial level is important to avoid glitches, but during operation the output level is already controlled by the driver. Including it in the configuration would mean either of the following:
We have an alternative way of specifying the output level, which is not ideal
Or, we would have to ignore a configuration field, which is not ideal
The text was updated successfully, but these errors were encountered:
Maybe we can also see if we can make config application completely infallible, might be worth exploring. Looking at the esp-idf gpio API, it seems most (all?) the errors returned are INVALID_ARG where someone passes a pin that doesn't exist in (and maybe where a pin can't go into a specific mode like some inputs on the esp32).
The points to think about:
The text was updated successfully, but these errors were encountered: