summaryrefslogtreecommitdiffstats
path: root/meta-rcar-gen3/recipes-bsp/arm-trusted-firmware
AgeCommit message (Collapse)AuthorFilesLines
2017-11-24rcar-gen3: IPL: Update SRCREV to follow the latest versionThuy Tran1-1/+2
This commit updates IPL components versions as below: - Update IPL and Secure Monitor Rev1.0.17 rev2. - Update optee_os Rev1.0.10. Signed-off-by: Thuy Tran <thuy.tran.xh@rvc.renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-08-25rcar-gen3: IPL: Update SRCREV to follow the latest versionThao Nguyen1-1/+1
This commit updates IPL components versions as below: - Update IPL and Secure Monitor Rev1.0.16 rev4. - Update optee_os to Rev1.0.9 rev2. - Update optee_linuxdriver to Rev1.0.7 rev2. Signed-off-by: Thao Nguyen <thao.nguyen.yb@renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-06-21rcar-gen3: arm-trusted-firmware: Update SRCREV to follow latest versionThao Nguyen1-1/+1
This commit updates IPL and Secure Monitor to Rev1.0.15 rev3. Signed-off-by: Thao Nguyen <thao.nguyen.yb@renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-04-19rcar-gen3: arm-trusted-firmware: Set PMIC_LEVEL_MODE to 0 for ULCBYusuke Goda1-1/+1
The operation mode of the PMIC for Salvator-X and ULCB are different: - ULCB : PULSE MODE (PMIC_LEVEL_MODE=0) - Salvator-X : LEVEL MODE (PMIC_LEVEL_MODE=1(default)) This commit updates arm-trusted-firmware recipe to check PMIC_LEVEL_MODE option and to control the corresponding PMIC. Change-Id: I152c1286d525000f58c678ec37eb6aac9502ac45 Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-04-19rcar-gen3: IPL: Update IPL according to BSP v3.5.3Thao Nguyen1-1/+1
This commit changes following contents: - Update IPL and Secure Monitor Rev1.0.14 rev2. - Update optee_os Rev1.0.8. Change-Id: Ibc16e31545b762451eb3704f817cd0d53fc1a50d Signed-off-by: Thao Nguyen <thao.nguyen.yb@rvc.renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-03-27rcar-gen3: arm-trusted-firmware: Set RCAR_GEN3_ULCB to 1 for ULCBYusuke Goda1-1/+2
This commit is to add judge state for ULCB. If machine is ulcb, "RCAR_GEN3_ULCB=1" will be added to compile option. Change-Id: Ia05f33a4362c4a7a302c8c0fc5785415f27b15b5 Signed-off-by: Yusuke Goda <yusuke.goda.sx@renesas.com> Signed-off-by: Thao Nguyen <thao.nguyen.yb@rvc.renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-03-23rcar-gen3: IPL: Update IPL version according to BSP v3.5.2Thao Nguyen1-1/+1
This commit changes following contents: - Update IPL and Secure Monitor Rev1.0.13 rev2. - Update optee_os Rev1.0.7 rev2. Change-Id: I0feeaad39dc13c79b7a2f2b8faaac4955413dcff Signed-off-by: Thao Nguyen <thao.nguyen.yb@rvc.renesas.com> Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>
2017-01-27First commit.Renesas-Yocto-v2.16.0Takamitsu Honda1-0/+55
Renesas BSP v3.5.1 (kernel v4.9 stable) [Environment] poky: yocto-2.1.2 (cca8dd15c8096626052f6d8d25ff1e9a606104a3) meta-openembedded: 55c8a76da5dc099a7bc3838495c672140cedb78e meta-linaro: 2f51d38048599d9878f149d6d15539fb97603f8f [Information] - U-boot: Changed load address from H'49000000 to H'50000000 - XDG_RUNTIME_DIR has been changed from "/run/user/root" to "/run/user/0" - Change location of include directory, which stores common user header files, to $(INCSHARED) - In BSP Only, core-image-weston is not supported even though local-wayland.conf is provided. - Please set Salvator-x SW7 Pin-1. In after Yocto BSP v2.12.0, it is 　necessary to enable BKUP_TRG signal for Suspend to RAM. - The dtb filename was changed in R-Car H3. Only "Image-r8a7795-es1-salvator-x.dtb" is supported in this version. Please use "Image-r8a7795-es1-salvator-x.dtb" It supports R-Car H3 WS1.0 and WS1.1. - Please update your local.conf and bblayers.conf corresponding to Yocto v2.16.0 package. You can refer to meta-rcargen3/docs/sample/conf/ for updated contents. - You have to re-compile out-of-recipe software like user application by v2.16.0 SDK toolchains. - In some boards, the resuming from System Suspend to RAM may cause unstable operation or failed to resume. Signed-off-by: Takamitsu Honda <takamitsu.honda.pv@renesas.com>