You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question: how to handle additional interrupts in software?
(I don't see currently an generic way of extending this. )
Currently the isr.c only handles the uart.
A possible API might look like:
int set_handler(unsigned int irq, void (*handler)(void));
void (*handler)(void) get_handler(unsigned int irq);
int remove_handler(unsigned int irq);
My hack for the moment is a callback function in the Litex isr routine shown below.
There is another pr for a different approach to this.
I've got a more traditional irq handler registration (proof of concept) in our tree I've been meaning to push for discussion.
Dear Litex community,
Question: how to handle additional interrupts in software?
(I don't see currently an generic way of extending this. )
Currently the isr.c only handles the uart.
A possible API might look like:
My hack for the moment is a callback function in the Litex isr routine shown below.
My little hack to extend the isr routine:
Code snippet using the callback function for my pps core:
The text was updated successfully, but these errors were encountered: