Traitify set_interrupt_handler?

[MabezDev]

I'm working on a proposal for a timer abstraction, and I think at some point we will also want to be able to say some struct implents InterruptConfigurable (or whatever) so that downstream code can enable interrupts and assign handlers generically. What do you think?

[brainstorm]

I'm working on a proposal for a timer abstraction, and I think at some point we will also want to be able to say some struct implents InterruptConfigurable (or whatever) so that downstream code can enable interrupts and assign handlers generically. What do you think?

Would that abstraction sit on embedded-hal (upstream) making it available for other ICs? I'm wondering how well it generalises and what was the initial motivation for this? Happy to check out your draft RFC if you have it published somewhere ;)

[MabezDev]

Would that abstraction sit on embedded-hal (upstream) making it available for other ICs?

I don't think so, no. This is something the WG briefly discussed at RustNL's unconf, and to achieve runtime configuration of interrupts it means the interrupt table needs to be placed in ram. The WG wasn't comfortable enforcing this on every device, as many have a very small amount of ram, so for the time being the default is to register interrupts at compile time with the ability to opt into runtime binding with a custom linker script.