| ecee0719 | 10-Oct-2025 |
Madhav Bhatt <madhav.bhatt@amd.com> |
fix(xilinx): remove PM_ABORT_SUSPEND API implementation
The API is not getting called by Linux. Removing it to reduce dead code and improve maintainability.
Note: This change removes code that is c
fix(xilinx): remove PM_ABORT_SUSPEND API implementation
The API is not getting called by Linux. Removing it to reduce dead code and improve maintainability.
Note: This change removes code that is common between versal and versal_net.
Change-Id: Ia7bfbcf2bbf80309beda7f8fa1ecf87de2591e2e Signed-off-by: Madhav Bhatt <madhav.bhatt@amd.com>
show more ...
|
| 34b9b3a9 | 10-Oct-2025 |
Yann Gautier <yann.gautier@st.com> |
Merge changes from topic "xlnx_enhance_tfa_feature_check" into integration
* changes: chore(xilinx): add deprecation warning to pm_feature_check refactor(xilinx): rename eemi_feature_check to tf
Merge changes from topic "xlnx_enhance_tfa_feature_check" into integration
* changes: chore(xilinx): add deprecation warning to pm_feature_check refactor(xilinx): rename eemi_feature_check to tfa_api_feature_check
show more ...
|
| 633cf6b7 | 01-Oct-2025 |
Naman Trivedi <naman.trivedimanojbhai@amd.com> |
fix(versal2): handle debugfs specific APIs before EEMI handler
In Versal Gen 2 SoC, all PM APIs use the extended SMC format including the debugfs-specific APIs. So, call eemi_psci_debugfs_handler be
fix(versal2): handle debugfs specific APIs before EEMI handler
In Versal Gen 2 SoC, all PM APIs use the extended SMC format including the debugfs-specific APIs. So, call eemi_psci_debugfs_handler before eemi_api_handler. This ensures that debugfs-specific PM APIs are handled correctly by TF-A and are not forwarded to the PLM firmware.
Change-Id: Ibab08c851c853a8f4272783b210040ddf7291d76 Signed-off-by: Naman Trivedi <naman.trivedimanojbhai@amd.com>
show more ...
|
| e25fad87 | 03-Oct-2025 |
Devanshi Chauhan <devanshi.chauhan@amd.com> |
refactor(xilinx): rename eemi_feature_check to tfa_api_feature_check
Rename eemi_feature_check() to tfa_api_feature_check() for better clarity. The new name clearly indicates its purpose of handling
refactor(xilinx): rename eemi_feature_check to tfa_api_feature_check
Rename eemi_feature_check() to tfa_api_feature_check() for better clarity. The new name clearly indicates its purpose of handling TF-A specific feature checks and improves code maintainability.
Change-Id: Ia74b12933427ccadbc8ede5ddc2a7a4822766264 Signed-off-by: Devanshi Chauhan <devanshi.chauhan@amd.com>
show more ...
|
| 4fd510e0 | 02-Sep-2025 |
Ronak Jain <ronak.jain@amd.com> |
feat(xilinx): use common SECURE/NON_SECURE macro
Remove platform-specific macro definitions such as SECURE_FLAG and NON_SECURE_FLAG, and replace them with the common macros SECURE and NON_SECURE acr
feat(xilinx): use common SECURE/NON_SECURE macro
Remove platform-specific macro definitions such as SECURE_FLAG and NON_SECURE_FLAG, and replace them with the common macros SECURE and NON_SECURE across all AMD-Xilinx platforms.
Change-Id: I95465e29ac8a9370da135c2113203c3206ecfec0 Signed-off-by: Ronak Jain <ronak.jain@amd.com>
show more ...
|
| 93434bdd | 09-Apr-2025 |
Ronak Jain <ronak.jain@amd.com> |
feat(xilinx): deprecate PM_REQ_SUSPEND EEMI API
Deprecate the use of the PM_REQ_SUSPEND EEMI API from the Versal, Versal-Net and Versal Gen 2 platforms. This is because the API is intended for suspe
feat(xilinx): deprecate PM_REQ_SUSPEND EEMI API
Deprecate the use of the PM_REQ_SUSPEND EEMI API from the Versal, Versal-Net and Versal Gen 2 platforms. This is because the API is intended for suspending cross-subsystems, and the same functionality can now be achieved using the ForcePowerdown API. Therefore, continuing to use PM_REQ_SUSPEND API may no longer be necessary. Hence deprecating the same.
Change-Id: I967d7803da4cf433fabfe8d87c32305954f69884 Signed-off-by: Ronak Jain <ronak.jain@amd.com>
show more ...
|
| 1d4372c4 | 12-Jun-2025 |
Jay Buddhabhatti <jay.buddhabhatti@amd.com> |
feat(versal): add support to clear PM specific data
During a kexec restart, only the kernel is reloaded while TF-A state remains unchanged, causing a mismatch between kernel and TF-A states. To reso
feat(versal): add support to clear PM specific data
During a kexec restart, only the kernel is reloaded while TF-A state remains unchanged, causing a mismatch between kernel and TF-A states. To resolve this, add support for the TF_A_CLEAR_PM_STATE API, which clears TF-A PM state.
Change-Id: I6b460f8cd4293381d3a9c574dd144521b8e54f8a Signed-off-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
show more ...
|
| 5cac1d85 | 20-Aug-2025 |
Ronak Jain <ronak.jain@amd.com> |
fix(xilinx): fix missing security flag in suspend path
Suspend flow was always programming wakeup sources with a fixed secure flag, regardless of whether the caller was secure or non-secure. This ma
fix(xilinx): fix missing security flag in suspend path
Suspend flow was always programming wakeup sources with a fixed secure flag, regardless of whether the caller was secure or non-secure. This may cause incorrect behavior for non-secure suspend requests.
Fix this by passing the caller's security state (flag) through pm_client_suspend() and pm_client_set_wakeup_sources() to ensure that wakeup sources are set with the correct context.
Fixes: <4697164a3fa8> ("plat: xilinx: versal: Mark IPI calls secure/non-secure")
Change-Id: I5fcf65788a54010b4759b0d08e4f54c6e5037e47 Signed-off-by: Ronak Jain <ronak.jain@amd.com>
show more ...
|
| 59047415 | 22-Aug-2025 |
Joanna Farley <joanna.farley@arm.com> |
Merge "fix(versal-net): add fallback on handoff failure" into integration |
| 4589ce0a | 05-Aug-2025 |
Naman Trivedi <naman.trivedimanojbhai@amd.com> |
feat(versal2): add support of MMI_GEM as wakeup source
Add MMI_GEM device node ID and add support of MMI_GEM as wakeup source.
Change-Id: I449e23df63e887978be1ff6d151542a27c44466f Signed-off-by: Na
feat(versal2): add support of MMI_GEM as wakeup source
Add MMI_GEM device node ID and add support of MMI_GEM as wakeup source.
Change-Id: I449e23df63e887978be1ff6d151542a27c44466f Signed-off-by: Naman Trivedi <naman.trivedimanojbhai@amd.com>
show more ...
|
| 05d0cb4f | 15-Jul-2025 |
Maheedhar Bollapalli <maheedharsai.bollapalli@amd.com> |
fix(versal-net): add fallback on handoff failure
On the Versal-Net platform, booting can fail during ELF loading due to the absence of a PLM handoff, preventing the system from booting further.
To
fix(versal-net): add fallback on handoff failure
On the Versal-Net platform, booting can fail during ELF loading due to the absence of a PLM handoff, preventing the system from booting further.
To address this, a fallback mechanism has been introduced that allows the boot process to continue even if the PLM handoff is not provided only in debug builds with jtag boot mode.
Change-Id: Ib8d92ab8400b7a63b05ae8c77b40b30fe7abaab8 Signed-off-by: Maheedhar Bollapalli <maheedharsai.bollapalli@amd.com>
show more ...
|
| 59eaed03 | 25-Jun-2025 |
Maheedhar Bollapalli <maheedharsai.bollapalli@amd.com> |
feat(versal2): parse reserve memory subnodes
In Versal Gen 2, TF-A parses the device tree to identify secure and non-secure memory regions, which are then used to validate the non-secure entry point
feat(versal2): parse reserve memory subnodes
In Versal Gen 2, TF-A parses the device tree to identify secure and non-secure memory regions, which are then used to validate the non-secure entry point address during a hot plug event
Change-Id: I8cdb098509bd3b06f0df5ea647220bdbb8a4bf35 Signed-off-by: Maheedhar Bollapalli <maheedharsai.bollapalli@amd.com>
show more ...
|
| c0719d21 | 16-May-2025 |
Devanshi Chauhan <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): add API to get powerdown request status
The pwrdwn_req_received variable is used across multiple platforms through extern keyword. Instead of using the extern, add getter API to access
fix(xilinx): add API to get powerdown request status
The pwrdwn_req_received variable is used across multiple platforms through extern keyword. Instead of using the extern, add getter API to access this variable across the platforms, and restrict the scope of variable to the particular file by defining it as static variable. This prevents unintended access of variable from other files and increase safety.
Change-Id: I758466ea7f6be2a90ec249dc3e4fa56cdbe11e57 Signed-off-by: Devanshi Chauhan <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| 2f8856fa | 06-Jun-2025 |
Naman Trivedi <naman.trivedimanojbhai@amd.com> |
fix(xilinx): add macro to extract node class from node ID
Introduce the NODECLASS() macro to extract the node class from a given node ID. This helps in filtering nodes based on their class as encode
fix(xilinx): add macro to extract node class from node ID
Introduce the NODECLASS() macro to extract the node class from a given node ID. This helps in filtering nodes based on their class as encoded in the ID.
Change-Id: I0e55b68a0103a99748df93b6fe9a3f1df4a7cca4 Signed-off-by: Naman Trivedi <naman.trivedimanojbhai@amd.com>
show more ...
|
| adbcd85e | 29-May-2025 |
Joanna Farley <joanna.farley@arm.com> |
Merge changes from topic "xlnx_versal_custom_sip" into integration
* changes: feat(versal): add hooks for mmap and early setup refactor(zynqmp): refactor custom sip service |
| 93db9e61 | 16-Apr-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 2.5 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.2.5: - A project should not contain unused macro declarations. - Fix: - Removed unus
fix(xilinx): resolve misra rule 2.5 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.2.5: - A project should not contain unused macro declarations. - Fix: - Removed unused macro declarations.
Change-Id: I2b9deda95d1a3927ab8b4e2c8a41bd85acb62be3 Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| 6df7184e | 10-Apr-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 4.6 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.4.6: - Typedefs that indicate size and signedness should be used in place of the b
fix(xilinx): resolve misra rule 4.6 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.4.6: - Typedefs that indicate size and signedness should be used in place of the basic numerical types. - Fix: - Used typedefs that indicate size and signedness in place of basic numerical types and updated return type of function wherever needed.
Change-Id: Ifde2379ee3f9d5ab30ef695d99f59591af575aba Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| f78c5970 | 10-Apr-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 12.2 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.12.2: - The right hand operand of a shift operator shall lie in the range zero to
fix(xilinx): resolve misra rule 12.2 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.12.2: - The right hand operand of a shift operator shall lie in the range zero to one less than the width in bits of the essential type of the left hand operand. - Fix: - Type casted left operand to a larger width than shift.
Change-Id: I662ff57e52d1260e2f1a0de595f19a9143714892 Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| c314a0b3 | 09-Apr-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 10.1 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.10.1: - Operands shall not be of an inappropriate essential type. - Fix: - Made ope
fix(xilinx): resolve misra rule 10.1 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.10.1: - Operands shall not be of an inappropriate essential type. - Fix: - Made operands of the same type.
Change-Id: I30a01cc0938603defba7572e9f4dd9ebe6d74a9c Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| 2993166d | 09-Apr-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 4.5 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.4.5: - Identifiers in the same name space with overlapping visibility should be ty
fix(xilinx): resolve misra rule 4.5 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.4.5: - Identifiers in the same name space with overlapping visibility should be typographically unambiguous. - Fix: - Renamed PM_RET_ERROR_NOFEATURE to PM_RET_ERROR_IOCTL_NOT_SUPPORTED and removed unnecessary macro definitions.
Change-Id: I6f03e619979685df7418fbccad7b0934d136776e Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| 55f6ea4d | 16-Apr-2025 |
Prasad Kummari <prasad.kummari@amd.com> |
refactor(zynqmp): refactor custom sip service
Refactored the custom SIP service code and relocated it to a common directory to support additional platforms and enhance code readability. Renamed ZYNQ
refactor(zynqmp): refactor custom sip service
Refactored the custom SIP service code and relocated it to a common directory to support additional platforms and enhance code readability. Renamed ZYNQMP_SIP_SVC_CUSTOM to a generic SOC_SIP_SVC_CUSTOM for better with other across SoCs
Change-Id: Id114f717d0397e257a831c7d5b67104c2c766d09 Signed-off-by: Prasad Kummari <prasad.kummari@amd.com>
show more ...
|
| 09abae06 | 24-Mar-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 2.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.2.3: - A project should not contain unused type declarations. - Fix: - Removed unuse
fix(xilinx): resolve misra rule 2.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.2.3: - A project should not contain unused type declarations. - Fix: - Removed unused code.
Change-Id: Ica5982fe83485da79ac18d45b44e66f5f37fb6e7 Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| eec03e94 | 21-Mar-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 8.6 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.8.6: - An identifier with external linkage shall have exactly one external definit
fix(xilinx): resolve misra rule 8.6 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.8.6: - An identifier with external linkage shall have exactly one external definition. - Fix: - Removed redundant function declarations since it is not defined.
Change-Id: If003efbfa08ee6ff4f545605ef34dfd16f33b664 Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| c35fe294 | 21-Mar-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 11.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.11.3: - A cast shall not be performed between a pointer to object type and a poin
fix(xilinx): resolve misra rule 11.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.11.3: - A cast shall not be performed between a pointer to object type and a pointer to a different object type. - Fix: - Removed unnecessary cast of pointers.
Change-Id: Iba5dbec0784dcaa86e3a00bd213cbc2711d12029 Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|
| 3df32f85 | 18-Mar-2025 |
Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com> |
fix(xilinx): resolve misra rule 8.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.8.3: - All declarations of an object or function shall use the same names and type
fix(xilinx): resolve misra rule 8.3 violations
Fixed below MISRA violation: - MISRA Violation: MISRA-C:2012 R.8.3: - All declarations of an object or function shall use the same names and type qualifiers. - Fix: - Made same name parameters and type qualifiers in function declaration and definition.
Change-Id: Idb4f986cec957102bb4ba1ef22f2e7937aaeb54d Signed-off-by: Devanshi Chauhan Alpeshbhai <devanshi.chauhanalpeshbhai@amd.com>
show more ...
|