Dave Marples d0cda60442 In the current implementation we only use very high priority interrupts (levels 0, 0x10 and 0x20 in CORTEX-M speak) but that means there are loads of lower priority ones that are effectively unused. I have *not* changed the semantics of these levels but have 'shifted' them to be based around the midpoint of the available interrupts (0x80) rather than at the top end....that allows for interrupts to be defined above (or, indeed, below) them as needed by the application. This should have no functional effect on existing code but adds in a clean capability to define higher priority interrupts.

2018-12-03 17:41:59 -06:00

..

chip.h

In the current implementation we only use very high priority interrupts (levels 0, 0x10 and 0x20 in CORTEX-M speak) but that means there are loads of lower priority ones that are effectively unused. I have *not* changed the semantics of these levels but have 'shifted' them to be based around the midpoint of the available interrupts (0x80) rather than at the top end....that allows for interrupts to be defined above (or, indeed, below) them as needed by the application. This should have no functional effect on existing code but adds in a clean capability to define higher priority interrupts.

2018-12-03 17:41:59 -06:00

efm32g_irq.h

arch/: Clean up some naming and spacing.

2018-06-20 15:38:06 -06:00

efm32gg_irq.h

arch/: Clean up some naming and spacing.

2018-06-20 15:38:06 -06:00

efm32tg_irq.h

arch/: Clean up some naming and spacing.

2018-06-20 15:38:06 -06:00

irq.h

arch/: Clean up some naming and spacing.

2018-06-20 15:38:06 -06:00