Hello Rouven, > -----Original Message----- > From: Rouven Czerwinski <r.czerwinski@xxxxxxxxxxxxxx> > Sent: Thursday, January 6, 2022 12:27 PM > To: ZHIZHIKIN Andrey <andrey.zhizhikin@xxxxxxxxxxxxxxxxxxxx>; linux- > kernel@xxxxxxxxxxxxxxx > Cc: peng.fan@xxxxxxx; ping.bai@xxxxxxx; alice.guo@xxxxxxx; agx@xxxxxxxxxxx; > frieder.schrempf@xxxxxxxxxx; leonard.crestez@xxxxxxx; festevam@xxxxxxxxx; > marex@xxxxxxx; herbert@xxxxxxxxxxxxxxxxxxx; horia.geanta@xxxxxxx; > aford173@xxxxxxxxx; krzk@xxxxxxxxxx; linux-imx@xxxxxxx; > devicetree@xxxxxxxxxxxxxxx; hongxing.zhu@xxxxxxx; s.hauer@xxxxxxxxxxxxxx; > pankaj.gupta@xxxxxxx; robh+dt@xxxxxxxxxx; thunder.leizhen@xxxxxxxxxx; > martink@xxxxxxxxx; daniel.baluta@xxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; > gregkh@xxxxxxxxxxxxxxxxxxx; shengjiu.wang@xxxxxxx; qiangqing.zhang@xxxxxxx; > michael@xxxxxxxx; op-tee@xxxxxxxxxxxxxxxxxxxxxxxxx; linux-crypto@xxxxxxxxxxxxxxx; > kernel@xxxxxxxxxxxxxx; jun.li@xxxxxxx; shawnguo@xxxxxxxxxx; davem@xxxxxxxxxxxxx; > l.stach@xxxxxxxxxxxxxx > Subject: Re: [PATCH v3 2/2] arm64: dts: imx8m: define proper status for caam jr > > Hi Andrey, > > On Wed, 2021-12-08 at 00:02 +0100, Andrey Zhizhikin wrote: > > CAAM JR nodes are configured by BootROM and are used by various software > > entities during the boot process before they reach the Kernel. > > > > Default BootROM configuration have JR0 and JR1 reserved for S-only > > access, while JR2 is generally available for both S and NS access. HAB > > feature of i.MX8M family does require that JR0 is reserved exclusively > > in S-only world, while JR1 and JR2 are both released to NS-World. OP-TEE > > can later reclaim the JR2 via dt_enable_secure_status() call, and modify > > the DID to hold it in S-World only. > > > > The above setup has been discovered during review of CAAM patchset > > presented to U-Boot integration [1], and does not correspond to the > > status on jr nodes in FDT. > > > > This missing status settings leads to the following error message during > > jr node probing: > > [ 1.509894] caam 30900000.crypto: job rings = 3, qi = 0 > > [ 1.525201] caam_jr 30901000.jr: failed to flush job ring 0 > > [ 1.525214] caam_jr: probe of 30901000.jr failed with error -5 > > > > JR register readout after BootROM execution shows the following values: > > JR0DID_MS = 0x8011 > > JR1DID_MS = 0x8011 > > JR2DID_MS = 0x0 > > > > This shows that JR0 and JR1 have TZ_OWN bit set, which marks them to be > > reserved for S-World, while JR2 remains accessible from NS-World. > > > > Provide the correct status for JR nodes in imx8m derivatives, which have > > a following meaning: > > - JR0: S-only > > - JR1: visible in both > > - JR2: NS-only > > > > Note, that JR2 is initially marked to be NS-only which does correspond > > to DID readout when OP-TEE is not present. Once present, OP-TEE will > > reclaim the JR2 and set both "status" and "secure-status" to claim JR2 > > for S-only access. > > While I can understand that you want to fix your use case for when HAB > is enabled, note that this is disabling JR0 in the none-HAB case as > well. This is not totally correct, as this patch does address the reservation of JR0 by BootROM in both HAB and non-HAB configurations. My current setup does not include HAB functionality enabled, and I still do observe boot errors that are listed in commit message. This is due to the fact that the BootROM does not release JR0 to NS-World regardless of whether HAB is enabled or not. This has been discussed in the U-Boot thread I provided the link in the patch. This patch does rather bring the correct HW module description as seeing from Linux. > IMO this should be handled correctly by the bootloader and/or OP- > TEE. The default upstream configuration for OP-TEE is to not use the > CAAM at runtime as well, since linux runtime PM disablement of the CAAM > will lock up OP-TEE when it tries to access the CAAM. If by handling you mean releasing JR0 reservation - then yes, it should be done by either SPL or TF-A as they do run in S World. In such a case, DTB bindings need to be adapted further according to the new state. Until this done - this patch does provide a correct state of HW to the Kernel. > > Kind regards, > Rouven Czerwinski > > > > > Signed-off-by: Andrey Zhizhikin <andrey.zhizhikin@xxxxxxxxxxxxxxxxxxxx> > > Link: [1]: https://lore.kernel.org/u-boot/AM6PR06MB4691FC905FE5658BE4B15C11A6609@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ > > --- > > Changes in V3: > > - No change, new patch introduced > > > > arch/arm64/boot/dts/freescale/imx8mm.dtsi | 4 ++++ > > arch/arm64/boot/dts/freescale/imx8mn.dtsi | 4 ++++ > > arch/arm64/boot/dts/freescale/imx8mp.dtsi | 4 ++++ > > arch/arm64/boot/dts/freescale/imx8mq.dtsi | 4 ++++ > > 4 files changed, 16 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8mm.dtsi > b/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > index 5b9c2cca9ac4..51465974c4ea 100644 > > --- a/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > +++ b/arch/arm64/boot/dts/freescale/imx8mm.dtsi > > @@ -914,18 +914,22 @@ sec_jr0: jr@1000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x1000 0x1000>; > > interrupts = <GIC_SPI 105 > IRQ_TYPE_LEVEL_HIGH>; > > + status = "disabled"; > > + secure-status = "okay"; > > }; > > > > sec_jr1: jr@2000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x2000 0x1000>; > > interrupts = <GIC_SPI 106 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "okay"; > > }; > > > > sec_jr2: jr@3000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x3000 0x1000>; > > interrupts = <GIC_SPI 114 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "disabled"; > > }; > > }; > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8mn.dtsi > b/arch/arm64/boot/dts/freescale/imx8mn.dtsi > > index ba23b416b5e6..e5edf14319b1 100644 > > --- a/arch/arm64/boot/dts/freescale/imx8mn.dtsi > > +++ b/arch/arm64/boot/dts/freescale/imx8mn.dtsi > > @@ -808,18 +808,22 @@ sec_jr0: jr@1000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x1000 0x1000>; > > interrupts = <GIC_SPI 105 > IRQ_TYPE_LEVEL_HIGH>; > > + status = "disabled"; > > + secure-status = "okay"; > > }; > > > > sec_jr1: jr@2000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x2000 0x1000>; > > interrupts = <GIC_SPI 106 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "okay"; > > }; > > > > sec_jr2: jr@3000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x3000 0x1000>; > > interrupts = <GIC_SPI 114 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "disabled"; > > }; > > }; > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8mp.dtsi > b/arch/arm64/boot/dts/freescale/imx8mp.dtsi > > index 977783784342..3c23bf5c3910 100644 > > --- a/arch/arm64/boot/dts/freescale/imx8mp.dtsi > > +++ b/arch/arm64/boot/dts/freescale/imx8mp.dtsi > > @@ -661,18 +661,22 @@ sec_jr0: jr@1000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x1000 0x1000>; > > interrupts = <GIC_SPI 105 > IRQ_TYPE_LEVEL_HIGH>; > > + status = "disabled"; > > + secure-status = "okay"; > > }; > > > > sec_jr1: jr@2000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x2000 0x1000>; > > interrupts = <GIC_SPI 106 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "okay"; > > }; > > > > sec_jr2: jr@3000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x3000 0x1000>; > > interrupts = <GIC_SPI 114 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "disabled"; > > }; > > }; > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi > b/arch/arm64/boot/dts/freescale/imx8mq.dtsi > > index 95d8b95d6120..16c4c9110ce7 100644 > > --- a/arch/arm64/boot/dts/freescale/imx8mq.dtsi > > +++ b/arch/arm64/boot/dts/freescale/imx8mq.dtsi > > @@ -999,18 +999,22 @@ sec_jr0: jr@1000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x1000 0x1000>; > > interrupts = <GIC_SPI 105 > IRQ_TYPE_LEVEL_HIGH>; > > + status = "disabled"; > > + secure-status = "okay"; > > }; > > > > sec_jr1: jr@2000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x2000 0x1000>; > > interrupts = <GIC_SPI 106 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "okay"; > > }; > > > > sec_jr2: jr@3000 { > > compatible = "fsl,sec-v4.0-job-ring"; > > reg = <0x3000 0x1000>; > > interrupts = <GIC_SPI 114 > IRQ_TYPE_LEVEL_HIGH>; > > + secure-status = "disabled"; > > }; > > }; > > > > -- > Pengutronix e.K. | Rouven Czerwinski | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | -- andrey
