Home
last modified time | relevance | path

Searched refs:peripheral (Results 1 – 13 of 13) sorted by relevance

/trusted-firmware-m-latest/platform/ext/target/nxp/lpcxpresso55s69/Native_Driver/drivers/
Dfsl_reset.c42 void RESET_SetPeripheralReset(reset_ip_name_t peripheral) in RESET_SetPeripheralReset() argument
44 const uint32_t regIndex = ((uint32_t)peripheral & 0xFFFF0000u) >> 16; in RESET_SetPeripheralReset()
45 const uint32_t bitPos = ((uint32_t)peripheral & 0x0000FFFFu); in RESET_SetPeripheralReset()
67 void RESET_ClearPeripheralReset(reset_ip_name_t peripheral) in RESET_ClearPeripheralReset() argument
69 const uint32_t regIndex = ((uint32_t)peripheral & 0xFFFF0000u) >> 16; in RESET_ClearPeripheralReset()
70 const uint32_t bitPos = ((uint32_t)peripheral & 0x0000FFFFu); in RESET_ClearPeripheralReset()
93 void RESET_PeripheralReset(reset_ip_name_t peripheral) in RESET_PeripheralReset() argument
95 RESET_SetPeripheralReset(peripheral); in RESET_PeripheralReset()
96 RESET_ClearPeripheralReset(peripheral); in RESET_PeripheralReset()
Dfsl_reset.h276 void RESET_SetPeripheralReset(reset_ip_name_t peripheral);
286 void RESET_ClearPeripheralReset(reset_ip_name_t peripheral);
296 void RESET_PeripheralReset(reset_ip_name_t peripheral);
306 static inline void RESET_ReleasePeripheralReset(reset_ip_name_t peripheral) in RESET_ReleasePeripheralReset() argument
308 RESET_ClearPeripheralReset(peripheral); in RESET_ReleasePeripheralReset()
/trusted-firmware-m-latest/docs/integration_guide/source_structure/
Dplatform_folder.rst14 on the platform. The name of the peripheral used by a service is set in its
27 If a platform doesn't support a peripheral, that is used by a service, then
28 the service cannot be used on the given platform. Using a peripheral in
/trusted-firmware-m-latest/docs/design_docs/
Dff_isolation.rst140 - If the memory device or the peripheral are shared between multiple hosts
142 to be available for validating accesses to that device or peripheral.
145 require a peripheral device. The memory-mapped region is regarded as
344 n equals the maximum peripheral numbers needed by one partition. This is
Dtfm_physical_attack_mitigation.rst272 Therefore, hindering the setup of memory or peripheral isolation hardware is an
287 - Manipulate peripheral configuration to give access to non-secure code to a
288 peripheral which is intended to be secure.
505 |--> platform specific peripheral isolation impl.
507 - Might make the important setting of peripheral config register redundant
/trusted-firmware-m-latest/docs/
Dglossary.rst102 Bus slave-side security controller for peripheral access.
/trusted-firmware-m-latest/docs/platform/nordic_nrf/nrf9160dk_nrf9160/
DREADME.rst56 * USB CDC ACM Serial Port bridged to the nRFx UART peripheral
/trusted-firmware-m-latest/docs/platform/nordic_nrf/nrf9161dk_nrf9161/
DREADME.rst56 * USB CDC ACM Serial Port bridged to the nRFx UART peripheral
/trusted-firmware-m-latest/docs/platform/nordic_nrf/nrf5340dk_nrf5340_cpuapp/
DREADME.rst64 * USB CDC ACM Serial Port bridged to the nRFx UART peripheral
/trusted-firmware-m-latest/docs/platform/lairdconnectivity/bl5340_dvk_cpuapp/
DREADME.rst66 * USB CDC ACM Serial Port bridged to the second UART peripheral
/trusted-firmware-m-latest/docs/design_docs/services/
Dsecure_partition_manager.rst210 The ``logging``-related peripheral can be set up **AT THIS STEP**, if
211 logging is enabled and it needs peripheral support. There is no standalone
288 signal into a specific partition, or customized peripheral settings.
/trusted-firmware-m-latest/docs/design_docs/software/
Dhardware_abstraction_layer.rst66 Partitions by using customized peripheral interfaces. To provide easier
775 The Secure Partition abstraction support will be introduced in the peripheral
/trusted-firmware-m-latest/docs/integration_guide/services/
Dtfm_secure_partition_addition.rst300 TF-M uses the below structure to indicate a peripheral memory.