Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-28 Thread Robin Murphy
On 28/02/18 17:53, Mark Rutland wrote: [...] It is not about to "check" the DT but if Linux could get access to the hardware. Hardware block assignment to secure or non-secure world could change at runtime for example I2C block could be manage by secure OS for a trusted application and when it

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-28 Thread Robin Murphy
On 28/02/18 17:53, Mark Rutland wrote: [...] It is not about to "check" the DT but if Linux could get access to the hardware. Hardware block assignment to secure or non-secure world could change at runtime for example I2C block could be manage by secure OS for a trusted application and when it

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-28 Thread Mark Rutland
On Wed, Feb 28, 2018 at 08:53:28AM +0100, Benjamin Gaignard wrote: > 2018-02-27 20:46 GMT+01:00 Robin Murphy : > > On 27/02/18 19:16, Benjamin Gaignard wrote: > >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : > >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100,

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-28 Thread Mark Rutland
On Wed, Feb 28, 2018 at 08:53:28AM +0100, Benjamin Gaignard wrote: > 2018-02-27 20:46 GMT+01:00 Robin Murphy : > > On 27/02/18 19:16, Benjamin Gaignard wrote: > >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : > >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: > > On

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
2018-02-27 20:46 GMT+01:00 Robin Murphy : > On 27/02/18 19:16, Benjamin Gaignard wrote: >> >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : >>> >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
2018-02-27 20:46 GMT+01:00 Robin Murphy : > On 27/02/18 19:16, Benjamin Gaignard wrote: >> >> 2018-02-27 18:11 GMT+01:00 Mark Rutland : >>> >>> On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1 platform is able to dedicate some hardware

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Robin Murphy
On 27/02/18 19:16, Benjamin Gaignard wrote: 2018-02-27 18:11 GMT+01:00 Mark Rutland : On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1 platform is able to dedicate some hardware blocks to a secure OS running in TrustZone. We

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Robin Murphy
On 27/02/18 19:16, Benjamin Gaignard wrote: 2018-02-27 18:11 GMT+01:00 Mark Rutland : On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: On early boot stages STM32MP1 platform is able to dedicate some hardware blocks to a secure OS running in TrustZone. We need to avoid using

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
2018-02-27 18:11 GMT+01:00 Mark Rutland : > On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: >> On early boot stages STM32MP1 platform is able to dedicate some hardware >> blocks >> to a secure OS running in TrustZone. >> We need to avoid using those

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
2018-02-27 18:11 GMT+01:00 Mark Rutland : > On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: >> On early boot stages STM32MP1 platform is able to dedicate some hardware >> blocks >> to a secure OS running in TrustZone. >> We need to avoid using those hardware blocks on

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Mark Rutland
On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: > On early boot stages STM32MP1 platform is able to dedicate some hardware > blocks > to a secure OS running in TrustZone. > We need to avoid using those hardware blocks on non-secure context (i.e. > kernel) > because read/write

Re: [PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Mark Rutland
On Tue, Feb 27, 2018 at 03:09:23PM +0100, Benjamin Gaignard wrote: > On early boot stages STM32MP1 platform is able to dedicate some hardware > blocks > to a secure OS running in TrustZone. > We need to avoid using those hardware blocks on non-secure context (i.e. > kernel) > because read/write

[PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
On early boot stages STM32MP1 platform is able to dedicate some hardware blocks to a secure OS running in TrustZone. We need to avoid using those hardware blocks on non-secure context (i.e. kernel) because read/write access will all be discarded. Extended TrustZone Protection driver register

[PATCH 0/3] STM32 Extended TrustZone Protection driver

2018-02-27 Thread Benjamin Gaignard
On early boot stages STM32MP1 platform is able to dedicate some hardware blocks to a secure OS running in TrustZone. We need to avoid using those hardware blocks on non-secure context (i.e. kernel) because read/write access will all be discarded. Extended TrustZone Protection driver register