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
..
Makefile	Merged in raiden00/nuttx (pull request #529)	2017-11-05 14:15:04 +00:00
stm32_adc.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_appinit.c	Fix another improperly qualified configuration varaible: CONFIG_HRTIM -> CONFIG_STM32_HRTIM. This is necessary to avoid conflict and confusion with other Kconfig files that may have the save variable definition.	2018-06-28 11:37:29 -06:00
stm32_autoleds.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_boot.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_buttons.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_comp.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_hrtim.c	Fix another improperly qualified configuration varaible: CONFIG_HRTIM -> CONFIG_STM32_HRTIM. This is necessary to avoid conflict and confusion with other Kconfig files that may have the save variable definition.	2018-06-28 11:37:29 -06:00
stm32_opamp.c	configs: add stm32f334-disco basic support	2017-07-21 18:01:20 +02:00
stm32_powerled.c	Fix another improperly qualified configuration varaible: CONFIG_HRTIM -> CONFIG_STM32_HRTIM. This is necessary to avoid conflict and confusion with other Kconfig files that may have the save variable definition.	2018-06-28 11:37:29 -06:00
stm32_smps.c	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
stm32f334-disco.h	Make sure that labeling is used consistently in all function headers.	2018-02-01 10:00:02 -06:00