Possible interrupt footgun on multicore systems

[MabezDev]

Now that the interrupt is handled internally by the peripheral driver, the interrupt is configured for the core the driver is created on, which means if core 0 creates a driver and moves it to core 1, its interrupt will still be handled by core 0. Maybe this isn't a big deal, but we should document or avoid it entirely if possible.

[bjoernQ]

Maybe it would be good to have a way to specify which core the interrupt should be handled on.

IIRC we are considering removing the interrupt handler from the constructors and add set_interrupt_handler for all drivers instead. I guess having an additional parameter wouldn't be too bad, then. (Alternatively specify that on the #[handler] macro - don't know why but that doesn't sound good to me)

[MabezDev]

Maybe it would be good to have a way to specify which core the interrupt should be handled on.

Unfortunately I don't think this is possible, at least on Xtensa. The mapping of interrupts can be done, but enable has be done each CPU respectively.

After thinking about this, I don't think this is a real issue. I will submit a docs PR to inform users about this, then we can close this.