Searched hist:"68 c4a16b37c797cf2a3d49af419f238e23cc8e4c" (Results 1 – 5 of 5) sorted by relevance
| /optee_os/core/arch/arm/plat-stm32mp1/drivers/ |
| H A D | stm32mp1_pwr.c | 68c4a16b37c797cf2a3d49af419f238e23cc8e4c Wed May 15 09:24:25 UTC 2019 Etienne Carriere <etienne.carriere@st.com> stm32mp1: use phys_to_virt_io_secure() where expected
This change updates platforms and drivers to use io_pa_or_va_secure()
when expecting a secure mapped address.
PWR, RCC, GIC, TAMP, BSEC, ETZPC, I2C are always secure (when embedded).
RNG uses a secure or non-secure mapping according to its registration in
platform shared_resource driver.
GPIOs IO memory is always access though non-secure mapped virtual
addresses.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/core/drivers/ |
| H A D | stm32_i2c.c | 68c4a16b37c797cf2a3d49af419f238e23cc8e4c Wed May 15 09:24:25 UTC 2019 Etienne Carriere <etienne.carriere@st.com> stm32mp1: use phys_to_virt_io_secure() where expected
This change updates platforms and drivers to use io_pa_or_va_secure()
when expecting a secure mapped address.
PWR, RCC, GIC, TAMP, BSEC, ETZPC, I2C are always secure (when embedded).
RNG uses a secure or non-secure mapping according to its registration in
platform shared_resource driver.
GPIOs IO memory is always access though non-secure mapped virtual
addresses.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | stm32_bsec.c | 68c4a16b37c797cf2a3d49af419f238e23cc8e4c Wed May 15 09:24:25 UTC 2019 Etienne Carriere <etienne.carriere@st.com> stm32mp1: use phys_to_virt_io_secure() where expected
This change updates platforms and drivers to use io_pa_or_va_secure()
when expecting a secure mapped address.
PWR, RCC, GIC, TAMP, BSEC, ETZPC, I2C are always secure (when embedded).
RNG uses a secure or non-secure mapping according to its registration in
platform shared_resource driver.
GPIOs IO memory is always access though non-secure mapped virtual
addresses.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| H A D | stm32_rng.c | 68c4a16b37c797cf2a3d49af419f238e23cc8e4c Wed May 15 09:24:25 UTC 2019 Etienne Carriere <etienne.carriere@st.com> stm32mp1: use phys_to_virt_io_secure() where expected
This change updates platforms and drivers to use io_pa_or_va_secure()
when expecting a secure mapped address.
PWR, RCC, GIC, TAMP, BSEC, ETZPC, I2C are always secure (when embedded).
RNG uses a secure or non-secure mapping according to its registration in
platform shared_resource driver.
GPIOs IO memory is always access though non-secure mapped virtual
addresses.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
| /optee_os/core/arch/arm/plat-stm32mp1/ |
| H A D | main.c | 68c4a16b37c797cf2a3d49af419f238e23cc8e4c Wed May 15 09:24:25 UTC 2019 Etienne Carriere <etienne.carriere@st.com> stm32mp1: use phys_to_virt_io_secure() where expected
This change updates platforms and drivers to use io_pa_or_va_secure()
when expecting a secure mapped address.
PWR, RCC, GIC, TAMP, BSEC, ETZPC, I2C are always secure (when embedded).
RNG uses a secure or non-secure mapping according to its registration in
platform shared_resource driver.
GPIOs IO memory is always access though non-secure mapped virtual
addresses.
Signed-off-by: Etienne Carriere <etienne.carriere@st.com>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|