J721e HS device support
Subsystems (2)
cover J721e HS device support
Hello all,
This series brings up High-Security (HS) device support on the J721e platform. Support for this K3 HS device is much like the existing AM65x HS and this series leverages much of that support.
There are also a couple tangentially related fixups that I noticed while adding this support and testing. Although not strictly needed they do allow J721e HS to just work out-of-box by the time the last patch adds the defconfigs.
Thanks,
Andrew
Andrew F. Davis (6):
configs: j721e_evm.h: Sync J721e environment configuration with AM65x
configs: ti: Factor out call to 'args_mmc' into MMC common environment
arm: K3: Fix header comment match AM6 specific file function
arm: K3: Disable ROM configured firewalls
arm: K3: Increase default SYSFW image size allocation
configs: Add configs for J721e High Security EVM
arch/arm/mach-k3/Kconfig | 2 +- arch/arm/mach-k3/am6_init.c | 28 +++++++- arch/arm/mach-k3/common.c | 30 ++++++++ arch/arm/mach-k3/common.h | 7 ++ arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++ configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ include/configs/j721e_evm.h | 16 ++++- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +- 10 files changed, 341 insertions(+), 8 deletions(-) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig
Signature · 1 line
2.17.1
PATCH 1/6 configs: j721e_evm.h: Sync J721e environment configuration with AM65x
Some of the environment configuration in AM65x is not available in J721e due to additions on one but not the other. These two platforms are similar enough these common definitions should be factored out to a common area, prepare for this by synchronizing them.
--- include/configs/j721e_evm.h | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
include/configs/j721e_evm.h +13 -3
@@ -60,10 +60,16 @@/* HyperFlash related configuration */ #define CONFIG_SYS_MAX_FLASH_BANKS_DETECT 1 +#define PARTS_DEFAULT \ +/* Linux partitions */ \ + "name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}\0" +/* U-Boot general configuration */ #define EXTRA_ENV_J721E_BOARD_SETTINGS \ "default_device_tree=" CONFIG_DEFAULT_DEVICE_TREE ".dtb\0" \ - "findfdt=setenv fdtfile ${default_device_tree}\0" \ + "findfdt=" \ + "setenv name_fdt ${default_device_tree};" \ + "setenv fdtfile ${name_fdt}\0" \ "loadaddr=0x80080000\0" \ "fdtaddr=0x82000000\0" \ "overlayaddr=0x83000000\0" \
@@ -80,7 +86,7 @@"bootdir=/boot\0" \"rd_spec=-\0" \"init_mmc=run args_all args_mmc\0" \ -"get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}\0" \ +"get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}\0" \"get_overlay_mmc=" \"fdt address ${fdtaddr};" \"fdt resize 0x100000;" \
@@ -90,7 +96,10 @@"fdt apply ${overlayaddr};" \"done;\0" \"get_kern_mmc=load mmc ${bootpart} ${loadaddr} " \ - "${bootdir}/${name_kern}\0" +"${bootdir}/${name_kern}\0" \ +"get_fit_mmc=load mmc ${bootpart} ${addr_fit} " \ +"${bootdir}/${name_fit}\0" \ + "partitions=" PARTS_DEFAULT#ifdef DEFAULT_RPROCS #undef DEFAULT_RPROCS
@@ -105,6 +114,7 @@/* Incorporate settings into the U-Boot environment */ #define CONFIG_EXTRA_ENV_SETTINGS \ DEFAULT_MMC_TI_ARGS \ + DEFAULT_FIT_TI_ARGS \ EXTRA_ENV_J721E_BOARD_SETTINGS \ EXTRA_ENV_J721E_BOARD_SETTINGS_MMC \ EXTRA_ENV_RPROC_SETTINGS \
Signature · 1 line
2.17.1
PATCH 2/6 configs: ti: Factor out call to 'args_mmc' into MMC common environment
In reply to Andrew F. DavisBoth 'loadfit' and 'mmcloados' start with a call to 'args_mmc' so this can be factored out to before eithers only call site. This also allows us to remove that call from 'loadfit', which should not have been calling it anyway as that command should not be MMC specific. Without the call to 'args_mmc' the command 'loadfit' becomes just a call to 'run_fit' so remove the indirection and call 'run_fit' directly, this removes the need for 'loadfit' command (which was misnamed anyway). Drop it.
--- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +++-- 2 files changed, 3 insertions(+), 3 deletions(-)
include/configs/ti_armv7_common.h +0 -1
@@ -61,7 +61,6 @@"setenv overlaystring ${overlaystring}'#'${overlay};" \"done;\0" \"run_fit=bootm ${addr_fit}#${fdtfile}${overlaystring}\0" \ -"loadfit=run args_mmc; run run_fit;\0" \/* * DDR information. If the CONFIG_NR_DRAM_BANKS is not defined,
include/environment/ti/mmc.h +3 -2
@@ -41,7 +41,7 @@"fi;" \"fi;" \"fi;\0" \ -"mmcloados=run args_mmc; " \ +"mmcloados=" \"if test ${boot_fdt} = yes || test ${boot_fdt} = try; then " \"if run loadfdt; then " \"bootz ${loadaddr} - ${fdtaddr}; " \
@@ -61,8 +61,9 @@"if mmc rescan; then " \"echo SD/MMC found on device ${mmcdev};" \"if run loadimage; then " \ +"run args_mmc; " \"if test ${boot_fit} -eq 1; then " \ -"run loadfit; " \ +"run run_fit; " \"else " \"run mmcloados;" \"fi;" \
Signature · 1 line
2.17.1
PATCH 3/6 arm: K3: Fix header comment match AM6 specific file function
In reply to Andrew F. DavisThis file used to be the common location for K3 init when AM6 was the only device, but common code was moved to common.c and this file became AM6 specific, correct this header text.
--- arch/arm/mach-k3/am6_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/mach-k3/am6_init.c +1 -1
@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-2.0+ /* -* K3: Architecture initialization +* AM6: SoC specific initialization * * Copyright (C) 2017-2018 Texas Instruments Incorporated - http://www.ti.com/ * Lokesh Vutla <[email protected]>
Signature · 1 line
2.17.1
PATCH 4/6 arm: K3: Disable ROM configured firewalls
In reply to Andrew F. DavisROM configures certain firewalls based on its usage, which includes the one in front of boot peripherals. In specific case of boot peripherals, ROM does not open up the full address space corresponding to the peripherals. Like in OSPI, ROM only configures the firewall region for 32 bit address space and mark 64bit address space flash regions as in-accessible.
When security-cfg is initialized by sysfw, all the non-configured firewalls are kept in bypass state using a global setting. Since ROM configured firewalls for certain peripherals, these will not be touched. So when bootloader touches any of the address space that ROM marked as in-accessible, system raises a firewall exception causing boot hang.
It would have been ideal if sysfw cleans up the ROM configured boot peripheral firewalls. Given the memory overhead to store this information provided by ROM and the boot time increase in re configuring the firewalls, it is concluded to clean this up in bootloaders.
So disable all the firewalls that ROM doesn't open up the full address space.
--- arch/arm/mach-k3/am6_init.c | 26 ++++++++++++++++++ arch/arm/mach-k3/common.c | 30 ++++++++++++++++++++ arch/arm/mach-k3/common.h | 7 +++++ arch/arm/mach-k3/j721e_init.c | 52 +++++++++++++++++++++++++++++++++++ 4 files changed, 115 insertions(+)
arch/arm/mach-k3/am6_init.c +26 -0
@@ -19,6 +19,26 @@#include <linux/soc/ti/ti_sci_protocol.h> #ifdef CONFIG_SPL_BUILD +#ifdef CONFIG_K3_LOAD_SYSFW +#ifdef CONFIG_TI_SECURE_DEVICE +struct fwl_data main_cbass_fwls[] = { + {"MMCSD1_CFG" ,2057 ,1 }, + {"MMCSD0_CFG" ,2058 ,1 }, + {"USB3SS0_SLV0" ,2176 ,2 }, + {"PCIE0_SLV" ,2336 ,8 }, + {"PCIE1_SLV" ,2337 ,8 }, + {"PCIE0_CFG" ,2688 ,1 }, + {"PCIE1_CFG" ,2689 ,1 }, +}, mcu_cbass_fwls[] = { + {"MCU_ARMSS0_CORE0_SLV" ,1024 ,1 }, + {"MCU_ARMSS0_CORE1_SLV" ,1028 ,1 }, + {"MCU_FSS0_S1" ,1033 ,8 }, + {"MCU_FSS0_S0" ,1036 ,8 }, + {"MCU_CPSW0" ,1220 ,1 }, +}; +#endif +#endif +static void mmr_unlock (u32 base,u32 partition) {/* Translate the base address */
@@ -108,6 +128,12 @@ void board_init_f(ulong dummy)* output. */ k3_sysfw_loader (preloader_console_init); + +/* Disable ROM configured firewalls right after loading sysfw */ +#ifdef CONFIG_TI_SECURE_DEVICE +remove_fwl_configs (main_cbass_fwls,ARRAY_SIZE (main_cbass_fwls)); +remove_fwl_configs (mcu_cbass_fwls,ARRAY_SIZE (mcu_cbass_fwls)); +#endif #else /* Prepare console output */ preloader_console_init ();
arch/arm/mach-k3/common.c +30 -0
@@ -244,3 +244,33 @@ void board_prep_linux(bootm_headers_t *images) CONFIG_SYS_CACHELINE_SIZE)); }#endif + +void remove_fwl_configs (struct fwl_data *fwl_data,size_t fwl_data_size) +{ +struct ti_sci_msg_fwl_region region; +struct ti_sci_fwl_ops *fwl_ops; +struct ti_sci_handle *ti_sci; +size_t i, j; + + ti_sci =get_ti_sci_handle (); + fwl_ops = &ti_sci->ops.fwl_ops; +for (i =0 ; i < fwl_data_size; i++) { +for (j =0 ; j < fwl_data[i].regions; j++) { + region.fwl_id = fwl_data[i].fwl_id; + region.region = j; + region.n_permission_regs =3 ; + + fwl_ops->get_fwl_region (ti_sci, ®ion); + +if (region.control !=0 ) { +pr_debug ("Attempting to disable firewall %5d (%25s)\n" , + region.fwl_id, fwl_data[i].name); + region.control =0 ; + +if (fwl_ops->set_fwl_region (ti_sci, ®ion)) +pr_err ("Could not disable firewall %5d (%25s)\n" , + region.fwl_id, fwl_data[i].name); + } + } + } +}
arch/arm/mach-k3/common.h +7 -0
@@ -14,5 +14,12 @@#define REV_PG1_0 0#define REV_PG2_0 1 +struct fwl_data { +const char *name; +u16 fwl_id; +u16 regions; +}; +void setup_k3_mpu_regions (void );int early_console_init (void ); +void remove_fwl_configs (struct fwl_data *fwl_data,size_t fwl_data_size);
arch/arm/mach-k3/j721e_init.c +52 -0
64 lines not on this page · raw message
Signature · 1 line
2.17.1
PATCH 5/6 arm: K3: Increase default SYSFW image size allocation
In reply to Andrew F. DavisThe memory allocated to store the FIT image containing SYSFW and board configuration data is statically defined to the largest size expected. This was 276000 bytes but now needs to be grown to 277000 to make room for the slightly larger SYSFW image used on J721e High-Security devices.
--- arch/arm/mach-k3/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/mach-k3/Kconfig +1 -1
@@ -119,7 +119,7 @@ config K3_SYSFW_IMAGE_MMCSD_RAW_MODE_PART config K3_SYSFW_IMAGE_SIZE_MAX int "Amount of memory dynamically allocated for loading SYSFW blob" depends on K3_LOAD_SYSFW - default 276000 + default 277000 help Amount of memory (in bytes) reserved through dynamic allocation at runtime for loading the combined System Firmware and configuration image
Signature · 1 line
2.17.1
PATCH 6/6 configs: Add configs for J721e High Security EVM
In reply to Andrew F. DavisAdd new defconfig files for the J721e High Security EVM.
These defconfigs are the same as for the non-secure part, except for:
CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_FIT_IMAGE_POST_PROCESS option set to 'y' CONFIG_SPL_FIT_IMAGE_POST_PROCESS option set to 'y' CONFIG_BOOTCOMMAND uses FIT images for booting
--- configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ 2 files changed, 208 insertions(+) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig
configs/j721e_hs_evm_a72_defconfig new file +106 -0
@@ -0,0 +1,106 @@ +CONFIG_ARM=y +CONFIG_ARCH_K3=y +CONFIG_TI_SECURE_DEVICE=y +CONFIG_SPL_LIBCOMMON_SUPPORT=y +CONFIG_SPL_LIBGENERIC_SUPPORT=y +CONFIG_SYS_MALLOC_F_LEN=0x8000 +CONFIG_SOC_K3_J721E=y +CONFIG_TARGET_J721E_A72_EVM=y +CONFIG_SPL_MMC_SUPPORT=y +CONFIG_SPL_SERIAL_SUPPORT=y +CONFIG_SPL_DRIVERS_MISC_SUPPORT=y +CONFIG_SPL_STACK_R_ADDR=0x82000000 +CONFIG_NR_DRAM_BANKS=2 +CONFIG_SPL_FS_FAT=y +CONFIG_SPL_LIBDISK_SUPPORT=y +CONFIG_SPL_SPI_FLASH_SUPPORT=y +CONFIG_SPL_SPI_SUPPORT=y +# CONFIG_PSCI_RESET is not set +CONFIG_SPL_TEXT_BASE=0x80080000 +CONFIG_DISTRO_DEFAULTS=y +# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set +CONFIG_FIT_IMAGE_POST_PROCESS=y +CONFIG_SPL_LOAD_FIT=y +CONFIG_SPL_FIT_IMAGE_POST_PROCESS=y +CONFIG_BOOTCOMMAND="run findfdt; run envboot; run init_${boot}; run boot_rprocs; run get_fit_${boot}; run get_overlaystring; run run_fit" +CONFIG_SPL_SYS_MALLOC_SIMPLE=y +CONFIG_SPL_STACK_R=y +CONFIG_SPL_SEPARATE_BSS=y +CONFIG_SPL_I2C_SUPPORT=y +CONFIG_SPL_DM_MAILBOX=y +CONFIG_SPL_DM_RESET=y +CONFIG_SPL_POWER_SUPPORT=y +CONFIG_SPL_POWER_DOMAIN=y +CONFIG_SPL_SPI_LOAD=y +CONFIG_SYS_SPI_U_BOOT_OFFS=0x280000 +CONFIG_SPL_YMODEM_SUPPORT=y +CONFIG_CMD_ASKENV=y +# CONFIG_CMD_FLASH is not set +CONFIG_CMD_MMC=y +CONFIG_CMD_MTD=y +CONFIG_CMD_REMOTEPROC=y +CONFIG_CMD_UFS=y +# CONFIG_CMD_SETEXPR is not set +CONFIG_CMD_TIME=y +CONFIG_CMD_EXT4_WRITE=y +CONFIG_MTDIDS_DEFAULT="nor0=47040000.spi.0,nor0=47034000.hyperbus" +CONFIG_MTDPARTS_DEFAULT="mtdparts=47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),- at 8m(hbmc.rootfs)" +# CONFIG_ISO_PARTITION is not set +# CONFIG_SPL_EFI_PARTITION is not set +CONFIG_OF_CONTROL=y +CONFIG_SPL_OF_CONTROL=y +CONFIG_DEFAULT_DEVICE_TREE="k3-j721e-common-proc-board" +CONFIG_SPL_MULTI_DTB_FIT=y +CONFIG_SPL_MULTI_DTB_FIT_NO_COMPRESSION=y +CONFIG_DM=y +CONFIG_SPL_DM=y +CONFIG_SPL_DM_SEQ_ALIAS=y +CONFIG_REGMAP=y +CONFIG_SPL_REGMAP=y +CONFIG_SYSCON=y +CONFIG_SPL_OF_TRANSLATE=y +CONFIG_CLK=y +CONFIG_SPL_CLK=y +CONFIG_CLK_TI_SCI=y +CONFIG_TI_SCI_PROTOCOL=y +CONFIG_DM_MAILBOX=y +CONFIG_K3_SEC_PROXY=y +CONFIG_MISC=y +CONFIG_DM_MMC=y +CONFIG_MMC_SDHCI=y +CONFIG_MMC_SDHCI_AM654=y +CONFIG_MTD=y +CONFIG_MTD_NOR_FLASH=y +CONFIG_MTD_DEVICE=y +CONFIG_FLASH_CFI_DRIVER=y +CONFIG_CFI_FLASH=y +CONFIG_SYS_FLASH_USE_BUFFER_WRITE=y +CONFIG_FLASH_CFI_MTD=y +CONFIG_SYS_FLASH_CFI=y +CONFIG_HBMC_AM654=y +CONFIG_DM_SPI_FLASH=y +CONFIG_SPI_FLASH_STMICRO=y +CONFIG_PINCTRL=y +# CONFIG_PINCTRL_GENERIC is not set +CONFIG_SPL_PINCTRL=y +# CONFIG_SPL_PINCTRL_GENERIC is not set +CONFIG_PINCTRL_SINGLE=y +CONFIG_POWER_DOMAIN=y +CONFIG_TI_SCI_POWER_DOMAIN=y +CONFIG_REMOTEPROC_TI_K3_DSP=y +CONFIG_REMOTEPROC_TI_K3_R5F=y +CONFIG_DM_RESET=y +CONFIG_RESET_TI_SCI=y +CONFIG_SCSI=y +CONFIG_DM_SCSI=y +CONFIG_DM_SERIAL=y +CONFIG_SPI=y +CONFIG_DM_SPI=y +CONFIG_CADENCE_QSPI=y +CONFIG_SYSRESET=y +CONFIG_SPL_SYSRESET=y +CONFIG_SYSRESET_TI_SCI=y +CONFIG_UFS=y +CONFIG_CADENCE_UFS=y +CONFIG_TI_J721E_UFS=y +CONFIG_OF_LIBFDT_OVERLAY=y
configs/j721e_hs_evm_r5_defconfig new file +102 -0
102 lines not on this page · raw message
Signature · 1 line
2.17.1
cover J721e HS device support
In reply to Andrew F. DavisQuoted 10 lines · Andrew F. Davis
Hello all,
This series brings up High-Security (HS) device support on the J721e platform. Support for this K3 HS device is much like the existing AM65x HS and this series leverages much of that support.
There are also a couple tangentially related fixups that I noticed while adding this support and testing. Although not strictly needed they do allow J721e HS to just work out-of-box by the time the last patch adds the defconfigs.
For the entire series:
Thank and regards,
Lokesh
Quoted 26 lines
Thanks,
AndrewAndrew F. Davis (6):
configs:j721e_evm.h: Sync J721e environment configuration with AM65x
configs: ti: Factor out call to 'args_mmc' into MMC common environment
arm: K3: Fix header comment match AM6 specific file function
arm: K3: Disable ROM configured firewalls
arm: K3: Increase default SYSFW image size allocation
configs: Add configs for J721e High Security EVMarch/arm/mach-k3/Kconfig | 2 +- arch/arm/mach-k3/am6_init.c | 28 +++++++- arch/arm/mach-k3/common.c | 30 ++++++++ arch/arm/mach-k3/common.h | 7 ++ arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++ configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ include/configs/j721e_evm.h | 16 ++++- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +- 10 files changed, 341 insertions(+), 8 deletions(-) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig
cover J721e HS device support
Hi Tom,
I see you have a -next again, if you don't want to take this for the v2020.01 perhaps this could be a good candidate for the next?
Andrew
Quoted 47 lines · Lokesh Vutla
Quoted 10 lines · Andrew F. Davis
Hello all,
This series brings up High-Security (HS) device support on the J721e platform. Support for this K3 HS device is much like the existing AM65x HS and this series leverages much of that support.
There are also a couple tangentially related fixups that I noticed while adding this support and testing. Although not strictly needed they do allow J721e HS to just work out-of-box by the time the last patch adds the defconfigs.
For the entire series:
Reviewed-by Lokesh Vutla <[email protected]>Thank and regards,
LokeshQuoted 26 lines
Thanks,
AndrewAndrew F. Davis (6):
configs:j721e_evm.h: Sync J721e environment configuration with AM65x
configs: ti: Factor out call to 'args_mmc' into MMC common environment
arm: K3: Fix header comment match AM6 specific file function
arm: K3: Disable ROM configured firewalls
arm: K3: Increase default SYSFW image size allocation
configs: Add configs for J721e High Security EVMarch/arm/mach-k3/Kconfig | 2 +- arch/arm/mach-k3/am6_init.c | 28 +++++++- arch/arm/mach-k3/common.c | 30 ++++++++ arch/arm/mach-k3/common.h | 7 ++ arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++ configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ include/configs/j721e_evm.h | 16 ++++- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +- 10 files changed, 341 insertions(+), 8 deletions(-) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig
cover J721e HS device support
Hi Tom,
Looks like -next wasn't used for this, ping on getting this into master now?
Thanks,
Andrew
Quoted 55 lines · Andrew F. Davis
Hi Tom,
I see you have a -next again, if you don't want to take this for the v2020.01 perhaps this could be a good candidate for the next?
Andrew
Quoted 47 lines · Lokesh Vutla
Quoted 10 lines · Andrew F. Davis
Hello all,
This series brings up High-Security (HS) device support on the J721e platform. Support for this K3 HS device is much like the existing AM65x HS and this series leverages much of that support.
There are also a couple tangentially related fixups that I noticed while adding this support and testing. Although not strictly needed they do allow J721e HS to just work out-of-box by the time the last patch adds the defconfigs.
For the entire series:
Reviewed-by Lokesh Vutla <[email protected]>Thank and regards,
LokeshQuoted 26 lines
Thanks,
AndrewAndrew F. Davis (6):
configs:j721e_evm.h: Sync J721e environment configuration with AM65x
configs: ti: Factor out call to 'args_mmc' into MMC common environment
arm: K3: Fix header comment match AM6 specific file function
arm: K3: Disable ROM configured firewalls
arm: K3: Increase default SYSFW image size allocation
configs: Add configs for J721e High Security EVMarch/arm/mach-k3/Kconfig | 2 +- arch/arm/mach-k3/am6_init.c | 28 +++++++- arch/arm/mach-k3/common.c | 30 ++++++++ arch/arm/mach-k3/common.h | 7 ++ arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++ configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ include/configs/j721e_evm.h | 16 ++++- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +- 10 files changed, 341 insertions(+), 8 deletions(-) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig
cover J721e HS device support
Quoted 4 lines · Andrew F. Davis
Hi Tom,
Looks like -next wasn't used for this, ping on getting this into master now?
Looks like a minor merge conflict now in master for this, I'll post a v2 to help with that.
Andrew
Quoted 59 lines
Thanks,
AndrewQuoted 55 lines · Andrew F. Davis
Hi Tom,
I see you have a -next again, if you don't want to take this for the v2020.01 perhaps this could be a good candidate for the next?
Andrew
Quoted 47 lines · Lokesh Vutla
Quoted 10 lines · Andrew F. Davis
Hello all,
This series brings up High-Security (HS) device support on the J721e platform. Support for this K3 HS device is much like the existing AM65x HS and this series leverages much of that support.
There are also a couple tangentially related fixups that I noticed while adding this support and testing. Although not strictly needed they do allow J721e HS to just work out-of-box by the time the last patch adds the defconfigs.
For the entire series:
Reviewed-by Lokesh Vutla <[email protected]>Thank and regards,
LokeshQuoted 26 lines
Thanks,
AndrewAndrew F. Davis (6):
configs:j721e_evm.h: Sync J721e environment configuration with AM65x
configs: ti: Factor out call to 'args_mmc' into MMC common environment
arm: K3: Fix header comment match AM6 specific file function
arm: K3: Disable ROM configured firewalls
arm: K3: Increase default SYSFW image size allocation
configs: Add configs for J721e High Security EVMarch/arm/mach-k3/Kconfig | 2 +- arch/arm/mach-k3/am6_init.c | 28 +++++++- arch/arm/mach-k3/common.c | 30 ++++++++ arch/arm/mach-k3/common.h | 7 ++ arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++ configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++ configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++ include/configs/j721e_evm.h | 16 ++++- include/configs/ti_armv7_common.h | 1 - include/environment/ti/mmc.h | 5 +- 10 files changed, 341 insertions(+), 8 deletions(-) create mode 100644 configs/j721e_hs_evm_a72_defconfig create mode 100644 configs/j721e_hs_evm_r5_defconfig