[riot-notifications] [RIOT-OS/RIOT] [WIP] cpu/atmega_common: pin change interrupt implementation (#11114)

Marian Buschsieweke notifications at github.com
Wed Mar 6 10:22:34 CET 2019

OK, I think using the "any pin on port" changed interrupt to transparently provide interrupts on pins that do not support a direct implementation is the portable way to do things. Being aware that this change has been somewhat controversial before, I would to have more than one ACK.

The main reason this change has been controversial (judging after a brief look into the previous discussions), is the requirements of ROM/RAM, which is a particularly scare resource on AVR boards. How about making this a pseudo module, so that each developer can decide if she/he does not more interrupt pins or not? In the end, this is a trade off (feature vs code size) that cannot be decided correctly by us for every use case.

Btw: Without having a deep understanding of the gory details: Has the issue with the port change interrupt being used for context switches been solved in the meantime?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190306/1b2da0b2/attachment.html>

More information about the notifications mailing list