digitalPinToInterrupt: fix double pin remapping on 2.x cores #10372
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
The
digitalPinToInterrupt()
macro currently remaps the pin number to the GPIO number. This is not necessary, as most users will then use the returned value inattachInterrupt()
or other similar API functions, which already perform the same remapping.The first half of the macro (the condition) does indeed require the remapping to ensure the check operates on GPIO numbers.
Related links
Fixes #10367 on 2.x (legacy) cores.
See also #10373 for the same fix on 3.x (current) cores.