One attachInterruptWakeup causes all interrupts to wake from deep sleep about arduinolowpower HOT 7 OPEN

This line makes the interrupt wakeup capable https://github.com/arduino-libraries/ArduinoLowPower/blob/master/src/samd/ArduinoLowPower.cpp#L93 , but it's also called in the core itself (https://github.com/arduino/ArduinoCore-samd/blob/master/cores/arduino/WInterrupts.c#L80) so once EIC clock is not stopped during sleep every configured pin can wakeup the board.
@cmaglie @sandeepmistry should we remove the wakeup setting from the core and leave it in the library only?

from arduinolowpower.

@facchinm I think that line was added for people not using the low power lib: arduino/ArduinoCore-samd#90

I'm ok with removing it, if you think it's best.

from arduinolowpower.

What about breaking older projects/sketches, which "rely" on this bug and are not using LowPower.attachInterruptWakeup on all required pins?

from arduinolowpower.

@trogper Can we include a warning at compile time?

from arduinolowpower.

@sslupsky I personally have used this library only once, so I won't be affected by the change.
How would you differentiate correct usage from incorrect?
When would you show the warning? Always?
Do Arduino users/programmers read warnings if the program compiles and works? (in other words: is warning appropriate?)
Wouldn't warning bother people who use it correctly?

from arduinolowpower.

Good points. Maybe the object can be changed so that when the method is called you specify which external interrupt is attached. The "default" can be "all"?

from arduinolowpower.

whatever solution is chosen, proper documentation will fix all issues and questions, i think.
another option would be to add an additional (optional) boolean parameter to attachInterrupt like standbyWakeupCapability or something like that. that way it stays in the core and is obvious to anyone who is attaching an interrupt.

from arduinolowpower.