Searched hist:"1 c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8" (Results 1 – 5 of 5) sorted by relevance
| /optee_os/core/drivers/firewall/ |
| H A D | stm32_iac.c | 1c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8 Tue Jan 02 10:35:59 UTC 2024 Gatien Chevallier <gatien.chevallier@foss.st.com> drivers: stm32_rif: add stm32_rif_access_violation_action()
This function should be used by peripherals capable on raising
access violation interrupts (SERC, IAC). The behavior of the platform
on such event is platform-specific. Therefore, its definition must be
done at platform level.
Also add CFG_STM32_PANIC_ON_IAC_EVENT and CFG_STM32_PANIC_ON_SERC_EVENT
to choose if the platform should panic upon receiving an IAC or a
SERC event.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Reviewed-by: Etienne Carriere <etienne.carriere@foss.st.com>
|
| H A D | stm32_serc.c | 1c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8 Tue Jan 02 10:35:59 UTC 2024 Gatien Chevallier <gatien.chevallier@foss.st.com> drivers: stm32_rif: add stm32_rif_access_violation_action()
This function should be used by peripherals capable on raising
access violation interrupts (SERC, IAC). The behavior of the platform
on such event is platform-specific. Therefore, its definition must be
done at platform level.
Also add CFG_STM32_PANIC_ON_IAC_EVENT and CFG_STM32_PANIC_ON_SERC_EVENT
to choose if the platform should panic upon receiving an IAC or a
SERC event.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Reviewed-by: Etienne Carriere <etienne.carriere@foss.st.com>
|
| /optee_os/core/include/drivers/ |
| H A D | stm32_rif.h | 1c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8 Tue Jan 02 10:35:59 UTC 2024 Gatien Chevallier <gatien.chevallier@foss.st.com> drivers: stm32_rif: add stm32_rif_access_violation_action()
This function should be used by peripherals capable on raising
access violation interrupts (SERC, IAC). The behavior of the platform
on such event is platform-specific. Therefore, its definition must be
done at platform level.
Also add CFG_STM32_PANIC_ON_IAC_EVENT and CFG_STM32_PANIC_ON_SERC_EVENT
to choose if the platform should panic upon receiving an IAC or a
SERC event.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Reviewed-by: Etienne Carriere <etienne.carriere@foss.st.com>
|
| /optee_os/core/arch/arm/plat-stm32mp2/ |
| H A D | main.c | 1c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8 Tue Jan 02 10:35:59 UTC 2024 Gatien Chevallier <gatien.chevallier@foss.st.com> drivers: stm32_rif: add stm32_rif_access_violation_action()
This function should be used by peripherals capable on raising
access violation interrupts (SERC, IAC). The behavior of the platform
on such event is platform-specific. Therefore, its definition must be
done at platform level.
Also add CFG_STM32_PANIC_ON_IAC_EVENT and CFG_STM32_PANIC_ON_SERC_EVENT
to choose if the platform should panic upon receiving an IAC or a
SERC event.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Reviewed-by: Etienne Carriere <etienne.carriere@foss.st.com>
|
| H A D | conf.mk | 1c32a0ea6beeeeaaef3ff7bf2e5d4015555dfae8 Tue Jan 02 10:35:59 UTC 2024 Gatien Chevallier <gatien.chevallier@foss.st.com> drivers: stm32_rif: add stm32_rif_access_violation_action()
This function should be used by peripherals capable on raising
access violation interrupts (SERC, IAC). The behavior of the platform
on such event is platform-specific. Therefore, its definition must be
done at platform level.
Also add CFG_STM32_PANIC_ON_IAC_EVENT and CFG_STM32_PANIC_ON_SERC_EVENT
to choose if the platform should panic upon receiving an IAC or a
SERC event.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Reviewed-by: Etienne Carriere <etienne.carriere@foss.st.com>
|