aboutsummaryrefslogtreecommitdiffstats
path: root/soc/j721e
Commit message (Collapse)AuthorAgeFilesLines
* sec-cfg: Add sa2ul_config sectionDave Gerlach2020-05-041-0/+9
| | | | | | | | | | | | Update the common.h headers to add new defines from SYSFW 2020.04. Starting from SYSFW v2020.04, an sa2ul_config section is mandatory in the security config. Otherwise the boot fails. Fix this by adding a section for sa2ul_config with all parameters configured to 0. Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
* sec-cfg: Add dkek_config sectionDave Gerlach2020-04-231-0/+11
| | | | | | | | | | | | | Update the common.h headers to add new defines from SYSFW 2020.03. Starting from SYSFW v2020.03, a dkek_config section is mandatory in the security config. Otherwise the boot fails. Fix this by adding a section for dkek_config with HOST_ID_ALL in allowed_hosts and allow_dkek_export_tisci set. Signed-off-by: Dave Gerlach <d-gerlach@ti.com> Tested-by: Suman Anna <s-anna@ti.com>
* j721e: Update to ABI 3.0 resource typesNikhil Devshatwar2020-04-032-1019/+1172
| | | | | | | | Update the J721E RM board configuration to use ABI 3.0 resource type definitions. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
* rm-cfg: j721e: Partition generic IR resource across core0/core1ti2020.00-rc1ti2020-rc1ti2019.06-rc5ti2019.06Nikhil Devshatwar2020-01-241-3/+3
| | | | | | | | | | | | | | | | | Main NAVSS interrupt router for MCU R5 subsystem is shared between both CPU cores. However, SYSFW models them to core specific devices where it appears that the interrupt router is dedicated for each core. MCU NAVSS IR is dedicated per MCU core but main NAVSS IR is not. Due to this, drivers calling GET_RANGE gets the same range on both cores, causing conflict in the interrupt partitioning. Fix this by partitioning the shared interrupt pool between MCU R5 core0 and core1. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* HACK: soc: j721e: Do not cross max limit for RM entriesNikhil Devshatwar2020-01-212-251/+6
| | | | | | | | | | | | | | Maximum number of entries supported in RM board config is currently limited to 276 (2 * RESASG_UTYPE_CNT) Any board config with more entries than this count will be rejected and causes boot failure. This needs to be fixed by increasing the max limit in SYSFW. In the absence of this bugfix, restrict the number of entries by folding all of R5, C6x, C7x host_id entries into single entry. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* soc: j721e: Partition nonsecure proxy and ring monitorsNikhil Devshatwar2020-01-212-3/+340
| | | | | | | | Define the resources for non secure proxy and ring monitor allocation across different hosts. Update the total count of resources. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* j721e: am65x: sec-cfg: Add otp_config sectionNikhil Devshatwar2020-01-211-1/+13
| | | | | | | | | | | | Update the common.h headers to add new defines from SYSFW 2019.12. Starting from SYSFW v2019.12, an otp_config section is mandatory in the security config. Otherwise the boot fails. Fix this by adding a section for opt_config with no other host having permission to OTP array. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* build: Add support for enabling sysfw tracesLokesh Vutla2019-08-291-0/+11
| | | | | | | | | | | | | Sysfw provides a provision for enabling sysfw traces while booting. This has to be enabled in board-cfg. In order to ease debug, enable the sysfw trace support with the help of a build option. Use the option to enable it: $ make ENABLE_TRACE=1 Reported-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
* HACK: j721e: rm-cfg: Use HOST_ALL for ethernet firmware flowsti2019.03-rc4ti2019.03-rc3ti2019.03-rc2ti2019.03Nikhil Devshatwar2019-08-132-9/+2
| | | | | | | | | | | | | | | Ethernet firmware acts as server for providing networking functionality to other clients. It allocates few flows from its pool for the client and then retuns the same to the client. Client does not own the resource it is borrowing from server and currently SYSFW lacks any APIs to allow shared ownership of this resource dyanmically. In absence of such an API, mark the ethernet firmware flows are HOST_ALL so that clients can call FLOW_CONFIG with the borrowed flow. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* j721e: rm-cfg: Partition GPIO interrupt routerNikhil Devshatwar2019-08-122-2/+9
| | | | | | | | Currently the Main GPIO interrupt router is only assigned to A72_2. Partition the IR lines such that few lines are assigned to A72_3 for usage from another Virtual machine. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* j721e: rm-cfg: Add resources for secure context of MCU R5Vignesh Raghavendra2019-07-312-1/+43
| | | | | | | | | | ROM boots up MCU R5 in secure context and R5 SPL continues to run in the same context. In order for R5 SPL to use DMA (e.g: with OSPI) add MCU NAVSS resources with MCU R5 secure host ID that is used by R5 SPL. Resources allocated are same as those allocated for non secure context. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
* j721e: board-cfg: Drop MSMC cache size from 4MB to 3MBti2019.02-rc4ti2019.02Andreas Dannenberg2019-07-111-1/+1
| | | | | | | | | | Reduce the amount of MSMC memory allocated by System Firmware for the main compute cluster's L3 cache from 4MB to 3MB. Signed-off-by: Andreas Dannenberg <dannenberg@ti.com> Acked-by: Nishanth Menon <nm@ti.com> Acked-by: Sunita Nadampalli <sunitan@ti.com> Acked-by: Carlos Hernandez <ceh@ti.com>
* j721e: rm-cfg: Start MAIN_0_R5_2 Tx and Rx at same levelNikhil Devshatwar2019-07-082-22/+7
| | | | | | | | | | | | | | | Channel allocation for MAIN_0_R5_2 is done such that Main NAV UDMA Tx and Rx channels start with different offsets. This cannot be used for block copy carveout since the Tx and Rx channels are not overlapping at start or end of the range. Fix this by allocating more channels to MAIN_0_R5_0 so that the MAIN_0_R5_2 channel ranges start at same value. Autogen table takes care of the corresponding ring allocations as well. Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* j721e: rm-cfg: Updated 2019.02 RM configNikhil Devshatwar2019-07-082-734/+941
| | | | | | | | | | | | | | This is auto generated RM config file to describe the resource partitioning for 2019.02 use cases. * Assign few channels/rings for A72_3 to be used by VMs * Assign extended channels for DRU/VPAC/DMPAC * Adjust resources for Main R5_0_1 for ethernet firmware * Reduce resources for R5_1_* cores since nothing is running there * Update the resource entry count Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com> Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
* Introduce initial J721E EVM supportAndreas Dannenberg2019-06-105-0/+1956
Add the consolidated configuration files that were arrived at during J721E silicon wakeup. Note that SYSFW debug trace both to memory as well as to the UART is disabled in alignment with the production configuration used on AM65x. If debug trace output is desired during development refer to the SYSFW release documentation (referenced in the included README.md file) discussion related to 'trace_dst_enables' and 'trace_src_enables'. Signed-off-by: Andreas Dannenberg <dannenberg@ti.com> Reviewed-by: Suman Anna <s-anna@ti.com> Cc: Nishanth Menon <nm@ti.com> Cc: Peter Ujfalusi <peter.ujfalusi@ti.com> Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Nikhil Devshatwar <nikhil.nd@ti.com>
    generated by cgit v1.2.3 (git 2.25.1)