| 8a26478f | 07-Aug-2023 |
Manish V Badarkhe <manish.badarkhe@arm.com> |
Merge "chore(xilinx): correct kernel doc warnings for missing functions" into integration |
| 16f19ed1 | 07-Aug-2023 |
Manish V Badarkhe <manish.badarkhe@arm.com> |
Merge changes from topic "xlnx_zynmp_tsp" into integration
* changes: chore(zynqmp): remove unused configuration from TSP fix(zynqmp): resolve runtime error in TSP |
| 83891729 | 07-Aug-2023 |
Manish V Badarkhe <manish.badarkhe@arm.com> |
Merge "fix(xilinx): add headers to resolve compile time issue" into integration |
| 744d60aa | 19-Jul-2023 |
Akshay Belsare <akshay.belsare@amd.com> |
fix(xilinx): add headers to resolve compile time issue
Add common/debug.h and libfdt.h files to the common file for XILINX_OF_BOARD_DTB_ADDR configuration.
Signed-off-by: Akshay Belsare <akshay.bel
fix(xilinx): add headers to resolve compile time issue
Add common/debug.h and libfdt.h files to the common file for XILINX_OF_BOARD_DTB_ADDR configuration.
Signed-off-by: Akshay Belsare <akshay.belsare@amd.com> Change-Id: I577cc018eda34e186e48594a62c54eb55f11bbd3
show more ...
|
| e5955d7c | 02-Aug-2023 |
Ronak Jain <ronak.jain@amd.com> |
fix(xilinx): remove clock_setrate and clock_getrate api
As per the current code base, PM_CLOCK_SETRATE and PM_CLOCK_GETRATE APIs are not supported for the runtime operations in the firmware and the
fix(xilinx): remove clock_setrate and clock_getrate api
As per the current code base, PM_CLOCK_SETRATE and PM_CLOCK_GETRATE APIs are not supported for the runtime operations in the firmware and the TF-A it is already returning an error when there is any request to access these APIs. So, just removing the unused code to avoid the confusion around these APIs.
Also, there is no issue with the backward compatibility as these APIs were never used since implemented. Hence no need to bump up the version of the feature check API as well.
Signed-off-by: Ronak Jain <ronak.jain@amd.com> Change-Id: I444f973e62cd25aae2e7f697d808210b265106ad
show more ...
|
| ba554002 | 14-Jul-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(zynqmp): remove unused configuration from TSP
In ZynqMP, the function zynqmp_config_setup() is common between bl31 and bl32(TSP). This function initializes IPI configuration and prints the chi
chore(zynqmp): remove unused configuration from TSP
In ZynqMP, the function zynqmp_config_setup() is common between bl31 and bl32(TSP). This function initializes IPI configuration and prints the chip idcode and revision on the console, which is already done in bl31 and redundant in bl32(TSP).
Remove the legacy code, reading the chip idcode and revision information through direct register read.
Change-Id: I5da8e75a597ac9c4e1b56346e065d29e2be8787f Signed-off-by: Prasad Kummari <prasad.kummari@amd.com>
show more ...
|
| 81ad3b14 | 14-Jul-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
fix(zynqmp): resolve runtime error in TSP
TSP(bl32) requires secure interrupts to be handled at S-EL1. Enable the ZynqMP to handle secure interrupts in S-EL1 by setting GICV2_G0_FOR_EL3 to 0 in case
fix(zynqmp): resolve runtime error in TSP
TSP(bl32) requires secure interrupts to be handled at S-EL1. Enable the ZynqMP to handle secure interrupts in S-EL1 by setting GICV2_G0_FOR_EL3 to 0 in case of SPD=tspd build option.
For ZYNQMP_WDT_RESTART build option GICV2_G0_FOR_EL3 needs to be enabled and thus for ZynqMP GICV2_G0_FOR_EL3 is set to 1 by default. On GICv2, when GICV2_G0_FOR_EL3 is set to 1, Group 0 interrupts target EL3. This allows GICv2 platforms to enable features requiring EL3 interrupt type.
This also means that all GICv2 Group 0 interrupts are delivered to EL3, and the Secure Payload interrupts needs to be synchronously handed over to Secure EL1 for handling.
Change-Id: I7eb72c6588ab41730a74ece261050840646de037 Signed-off-by: Prasad Kummari <prasad.kummari@amd.com>
show more ...
|
| 6304759a | 19-Jul-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(xilinx): reorder headers in assembly files
In tf-a-ci-scripts repo, change commit 8ffa3d571b(ci(static-checks): correct include order for *.S macro headers) provides a fix related to header fi
chore(xilinx): reorder headers in assembly files
In tf-a-ci-scripts repo, change commit 8ffa3d571b(ci(static-checks): correct include order for *.S macro headers) provides a fix related to header file include order in assembly files. With the above fix, improper header order in assembly files has been detected.
Reorder the header includes in assembly files as per the update in tf-a-ci-scripts.
Signed-off-by: Prasad Kummari <prasad.kummari@amd.com> Change-Id: I4a4f3c5bb73886dae234160b893470443f1424fc
show more ...
|
| 421893a0 | 19-Jul-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(xilinx): correct kernel doc warnings for missing functions
In commit b9d26cd3c4 ("chore(xilinx): replace fsbl with xbl"), function and variable names were changed, but the corresponding functi
chore(xilinx): correct kernel doc warnings for missing functions
In commit b9d26cd3c4 ("chore(xilinx): replace fsbl with xbl"), function and variable names were changed, but the corresponding function name in the functional documentation comments is not updated. Update the function and variable names as per the above commit.
Signed-off-by: Prasad Kummari <prasad.kummari@amd.com> Change-Id: I7b777c21fe3673d29f809bf923eba38749f2c024
show more ...
|
| 46a08aab | 10-Jul-2023 |
Amit Nagal <amit.nagal@amd.com> |
feat(versal-net): ddr address reservation in dtb at runtime
When the TF-A is placed in DDR memory range, the DDR memory range needs to be explicitly reserved in the default device tree.
A new build
feat(versal-net): ddr address reservation in dtb at runtime
When the TF-A is placed in DDR memory range, the DDR memory range needs to be explicitly reserved in the default device tree.
A new build time parameter, XILINX_OF_BOARD_DTB_ADDR, is introduced. The TF-A will reserve the DDR memory only when a valid DTB address is provided to XILINX_OF_BOARD_DTB_ADDR during build.
Now the user has options, either manually reserve the desired DDR address range for TF-A in device tree or let TF-A access and modify the device tree, to reserve the DDR address range, in runtime using the build parameter.
Change-Id: I45a5d9a8343ea8a19ea014a70023731de94d061a Signed-off-by: Amit Nagal <amit.nagal@amd.com> Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| 56d1857e | 10-Jul-2023 |
Amit Nagal <amit.nagal@amd.com> |
feat(versal): ddr address reservation in dtb at runtime
When the TF-A is placed in DDR memory range, the DDR memory range needs to be explicitly reserved in the default device tree.
A new build tim
feat(versal): ddr address reservation in dtb at runtime
When the TF-A is placed in DDR memory range, the DDR memory range needs to be explicitly reserved in the default device tree.
A new build time parameter, XILINX_OF_BOARD_DTB_ADDR, is introduced. The TF-A will reserve the DDR memory only when a valid DTB address is provided to XILINX_OF_BOARD_DTB_ADDR during build.
Now the user has options, either manually reserve the desired DDR address range for TF-A in device tree or let TF-A access and modify the device tree, to reserve the DDR address range, in runtime using the build parameter.
Change-Id: I4442a90e1cab5a3a115f4eeb8a7e09e247189ff0 Signed-off-by: Amit Nagal <amit.nagal@amd.com> Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| e7644eb6 | 04-Jul-2023 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "chore(xilinx): reorder include files as per TF-A guidelines" into integration |
| 38a05485 | 04-Jul-2023 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "fix(versal-net): correct device node indexes" into integration |
| 66b5620c | 28-Jun-2023 |
Jay Buddhabhatti <jay.buddhabhatti@amd.com> |
fix(versal-net): correct device node indexes
Currently, the peripheral node indexes are incorrect for Versal NET due to which incorrect node error is generated and permission to set the device as wa
fix(versal-net): correct device node indexes
Currently, the peripheral node indexes are incorrect for Versal NET due to which incorrect node error is generated and permission to set the device as wakeup source is failed. Correct Versal NET peripheral node indexes to fix above issue.
Fixes: 662aafd6475e ("feat(xilinx): add device node indexes") Change-Id: I4a2d76f375645e13512599a0272d9322ff6fafd3 Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
show more ...
|
| a0a4d86c | 22-Jun-2023 |
Akshay Belsare <akshay.belsare@amd.com> |
chore(xilinx): update warning message
Update the Warning message to be more informative about the warning being printed.
Change-Id: I923dc5dd760908844d5e1ac8542fd1b04c9f0af5 Signed-off-by: Akshay B
chore(xilinx): update warning message
Update the Warning message to be more informative about the warning being printed.
Change-Id: I923dc5dd760908844d5e1ac8542fd1b04c9f0af5 Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| 01c8c6a5 | 15-Jun-2023 |
Akshay Belsare <akshay.belsare@amd.com> |
feat(versal-net): add cluster check in handoff parameters
Versal NET platform supports multiple cpu clusters and the cluster information for every partition contaning firmware component is being pas
feat(versal-net): add cluster check in handoff parameters
Versal NET platform supports multiple cpu clusters and the cluster information for every partition contaning firmware component is being passed by PLM through handoff parameters to TF-A.
Function implementation for getting cluster value for the firmware component partition in TF-A and check for the firmware component being targeted to be executed on Cluster 0.
Signed-off-by: Akshay Belsare <akshay.belsare@amd.com> Change-Id: I8622699e12b0a9cda83ae46e2ad0a038ca377fda
show more ...
|
| a36ac40c | 07-Mar-2023 |
Akshay Belsare <akshay.belsare@amd.com> |
feat(versal-net): get the handoff params using IPI
Use the IPI command GET_HANDOFF_PARAM to get the PLM to TF-A handoff parameters. The BL32/BL33 information from the handoff parameters will be used
feat(versal-net): get the handoff params using IPI
Use the IPI command GET_HANDOFF_PARAM to get the PLM to TF-A handoff parameters. The BL32/BL33 information from the handoff parameters will be used by TF-A.
If no valid PLM to TF-A handoff parameters are available then, the TF-A will fall back to the build time information or defaults set in the TF-A for BL32/BL33.
Once the bootmode identification is supported the default configuration will be done only for JTAG and for all other bootmodes PLM to TF-A handoff parameters will be used.
Change-Id: Ia2204fe30fea6f32b4e5d2610820217e6ed23e4d Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| b9d26cd3 | 08-Jun-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(xilinx): replace fsbl with xbl
The handoff functionality is common between platforms and all platforms do not use fsbl terminology. Renaming handoff related code to generic naming.
Signed-off
chore(xilinx): replace fsbl with xbl
The handoff functionality is common between platforms and all platforms do not use fsbl terminology. Renaming handoff related code to generic naming.
Signed-off-by: Prasad Kummari <prasad.kummari@amd.com> Change-Id: Ic250af927f33c4fecbc2e6bab01b83a6dd2aab52 Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| 01a326ab | 22-Jun-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(xilinx): reorder include files as per TF-A guidelines
This commit reorders the include files in accordance with the guidelines provided by Trusted Firmware-A (TF-A). The include files are rear
chore(xilinx): reorder include files as per TF-A guidelines
This commit reorders the include files in accordance with the guidelines provided by Trusted Firmware-A (TF-A). The include files are rearranged to ensure a consistent and organized structure in the codebase, facilitating better readability and maintainability.
https: //trustedfirmware-a.readthedocs.io/en/latest/process/coding-style.html#headers-and-inclusion https://git.trustedfirmware.org/ci/tf-a-ci-scripts.git/tree/script/static-checks/
For example, to run header check: /tf-a-ci-scripts/script/static-checks/check-include-order.py --tree ${PWD} > Includefileorder.txt
Signed-off-by: Prasad Kummari <prasad.kummari@amd.com> Change-Id: Ia5802722e69859596b94f31ec40755adbf7d865b
show more ...
|
| de7ed953 | 09-Jun-2023 |
Prasad Kummari <prasad.kummari@amd.com> |
chore(xilinx): follow kernel doc format for functional documentation
For TF-A, there is no format specified for functional documentation. For AMD-Xilinx platforms, following kernel-doc format for th
chore(xilinx): follow kernel doc format for functional documentation
For TF-A, there is no format specified for functional documentation. For AMD-Xilinx platforms, following kernel-doc format for the functional documentation to make sure AMD-xilinx documentation is align with actual code.
For example use kernel-doc from linux to call: <linux>/scripts/kernel-doc -man -v 1 >/dev/null file...
Signed-off-by: Prasad Kummari <prasad.kummari@amd.com> Change-Id: Idcc9def408b6c8da35b36f67ef82fc00890e998c
show more ...
|
| 91291633 | 08-Jun-2023 |
Akshay Belsare <akshay.belsare@amd.com> |
fix(zynqmp): type cast addresses to fix overflow issue
Type cast the build time base and size argument to unsigned integer and the limit derived from these two as unsigned long to avoid size overflo
fix(zynqmp): type cast addresses to fix overflow issue
Type cast the build time base and size argument to unsigned integer and the limit derived from these two as unsigned long to avoid size overflow issue during build.
For zynqmp platform, calculating the limit without typecasting results in build error as follows
make -j DEBUG=0 RESET_TO_BL31=1 PLAT=zynqmp \ ZYNQMP_ATF_MEM_BASE=0x70000000 ZYNQMP_ATF_MEM_SIZE=0x10000000 \ XILINX_OF_BOARD_DTB_ADDR=0x100000 bl31
plat/xilinx/zynqmp/include/platform_def.h:51:62: error: integer overflow in expression of type 'int' results in '-2147483648' [-Werror=overflow] 51 | # define BL31_LIMIT (ZYNQMP_ATF_MEM_BASE + ZYNQMP_ATF_MEM_SIZE)
Change-Id: Id093a50e748884d4fba65626e94f361f6c23cecc Signed-off-by: Michal Simek <michal.simek@amd.com> Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|
| 06b9c4c8 | 12-Jun-2023 |
Jay Buddhabhatti <jay.buddhabhatti@amd.com> |
fix(versal): add missing irq mapping for wakeup src
The commit 0ec6c31320c6 provides irq to device index mapping which is required to check for IRQs and set peripheral as a wake source if IRQ is ena
fix(versal): add missing irq mapping for wakeup src
The commit 0ec6c31320c6 provides irq to device index mapping which is required to check for IRQs and set peripheral as a wake source if IRQ is enabled. But in that commit some IRQ numbers are missed. Because of that, wakeup using some peripheral interrupts will not work. Add those missing IRQ numbers.
Fixes: 0ec6c31320c6 ("feat(versal): replace irq array with switch case") Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com> Change-Id: Icbc773050c328be253702e63e7cf8450c7dee133
show more ...
|
| f51bbacf | 12-Jun-2023 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "fix(zynqmp): fix prepare_dtb() memory description" into integration |
| f1a32f49 | 07-Jun-2023 |
Manish Pandey <manish.pandey2@arm.com> |
Merge "chore(xilinx): replace ATF with TFA" into integration |
| 3efee73d | 02-Jun-2023 |
Michal Simek <michal.simek@amd.com> |
fix(zynqmp): fix prepare_dtb() memory description
The commit 8ce2fbffe37d ("fix(zynqmp): fix BLXX memory limits for user defined values") fixed logic around BL31_LIMIT but didn't update prepare_dtb(
fix(zynqmp): fix prepare_dtb() memory description
The commit 8ce2fbffe37d ("fix(zynqmp): fix BLXX memory limits for user defined values") fixed logic around BL31_LIMIT but didn't update prepare_dtb() which is also using +1 logic.
Change-Id: Ia6de10d992a552ca9cfa39c14261b0f94cda95ec Signed-off-by: Michal Simek <michal.simek@amd.com> Signed-off-by: Akshay Belsare <akshay.belsare@amd.com>
show more ...
|