Merge "fix(xilinx): correct node idx for Versal Gen 2" into integration

Merge changes I361f587a,Idc704ece,I5529dbe5 into integration

* changes:
fix(gic): init the GIC before the platform with a hook
refactor(arm): set the transfer list up earlier
refactor(el3-runt

Merge changes I361f587a,Idc704ece,I5529dbe5 into integration

* changes:
fix(gic): init the GIC before the platform with a hook
refactor(arm): set the transfer list up earlier
refactor(el3-runtime): use arm_gicr_base_addrs for sp-min

show more ...

Merge "fix(xilinx): use bool in control expressions" into integration

Merge changes from topic "amd_feat_dyn_core_clust" into integration

* changes:
feat(versal2): update plat psci based on dynamic core and cluster
feat(versal2): add dynamic fetching of core and c

Merge changes from topic "amd_feat_dyn_core_clust" into integration

* changes:
feat(versal2): update plat psci based on dynamic core and cluster
feat(versal2): add dynamic fetching of core and cluster
refactor(xilinx): promote map/unmap helpers to public scope
feat(versal2): use runtime core/cluster variables for dyn topology

show more ...

fix(xilinx): correct node idx for Versal Gen 2

Several device node indices are incorrectly placed in the common
section of the enum but are only used in Versal Gen 2:
- XPM_NODEIDX_DEV_I2C_2 through

fix(xilinx): correct node idx for Versal Gen 2

Several device node indices are incorrectly placed in the common
section of the enum but are only used in Versal Gen 2:
- XPM_NODEIDX_DEV_I2C_2 through XPM_NODEIDX_DEV_I2C_7 (0x117-0x11C)
- XPM_NODEIDX_DEV_CAN_FD_2, XPM_NODEIDX_DEV_CAN_FD_3 (0x11D-0x11E)
- XPM_NODEIDX_DEV_TTC_4 through XPM_NODEIDX_DEV_TTC_7 (0x11F-0x122)
- XPM_NODEIDX_DEV_MMI_GEM (0x13A)

This causes incorrect XPM_NODEIDX_DEV_MAX values:
- Versal: is 0x13B, should be 0x54
- Versal Gen 2: is 0xD8 (USB_1 came after MMI_GEM in source order),
should be 0x13B to include MMI_GEM

The incorrect MAX on Versal Gen 2 causes the bounds check in
pm_client_set_wakeup_sources() to silently reject MMI_GEM
(0x13A).

Move all Versal Gen 2-specific device indices inside the
XPM_NODEIDX_DEV_MAX:
- Versal: XPM_NODEIDX_DEV_MAX = 0x54
- Versal Net: XPM_NODEIDX_DEV_MAX = 0xDF (unchanged)
- Versal Gen 2: XPM_NODEIDX_DEV_MAX = 0x13B

Change-Id: I6979758b1295782a9743301d0ad7f7cda75d1b36
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

refactor(xilinx): promote map/unmap helpers to public scope

Remove the static qualifier from add_mmap_dynamic_region() and
remove_mmap_dynamic_region() in plat_fdt.c, and add their
declarations to p

refactor(xilinx): promote map/unmap helpers to public scope

Remove the static qualifier from add_mmap_dynamic_region() and
remove_mmap_dynamic_region() in plat_fdt.c, and add their
declarations to plat_fdt.h so they can be reused across Xilinx
platform code.

When XILINX_OF_BOARD_DTB_ADDR is not defined, static inline no-op
stubs are provided to allow unconditional calls without link errors.

Change-Id: I795dbcb2b13b4e5d5fe900edabaa703d6aade0be
Signed-off-by: Maheedhar Bollapalli <maheedharsai.bollapalli@amd.com>

show more ...

fix(versal2): resolve type mismatch

This corrects MISRA violation C2012-10.3:
The value of an expression shall not be assigned to an object with a
narrower essential type or of a different essential

fix(versal2): resolve type mismatch

This corrects MISRA violation C2012-10.3:
The value of an expression shall not be assigned to an object with a
narrower essential type or of a different essential type category.
Adjust macro definition to avoid implicit type conversion.

This corrects MISRA violation C2012-10.4:
Both operands of an operator in which the usual arithmetic
conversions are performed shall have the same essential type category.
Make operands of the same essential type category.

Change-Id: I66c18422b701515947c32b0aabfc3aec4bad3dff
Signed-off-by: Sai Varun Venkatapuram <saivarun.venkatapuram@amd.com>

show more ...

fix(xilinx): use bool in control expressions

This corrects the MISRA violation C2012-14.4:
The controlling expression of an if statement and the controlling
expression of an iteration-statement shal

fix(xilinx): use bool in control expressions

This corrects the MISRA violation C2012-14.4:
The controlling expression of an if statement and the controlling
expression of an iteration-statement shall have essentially Boolean
type.
Used boolean in control expressions for fixing this violation.

Change-Id: I29355f8f36c4a5fa88d1cc16656940f4c8cdf088
Signed-off-by: Suraj Kakade <suraj.hanumantkakade@amd.com>

show more ...

fix(gic): init the GIC before the platform with a hook

While GIC setup is generic across platforms, its usage is not. Some
platforms won't use it at EL3, while others need to configure interrupts
(l

fix(gic): init the GIC before the platform with a hook

While GIC setup is generic across platforms, its usage is not. Some
platforms won't use it at EL3, while others need to configure interrupts
(like RAS) in the standard platform hooks. To do that, the GIC needs to
be set up and ready to use before calling the platform hooks but
currently that is only done after. Annoyingly, a handful of platforms
need to set their GIC up before initialising it necessitating the
platform hooks to be called before GIC init.

This patch resolves this contradiction by moving the general GIC setup
calls to before the platform hooks and adding a GIC-specific platform
hook just before GIC per CPU init. This way both types of platforms can
do their business at the same time.

Change-Id: I361f587ab4603162ee880addb074800cbbb97b49
Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com>

show more ...

Merge "feat(versal): add support for TFA_NO_PM configuration" into integration

feat(versal): add support for TFA_NO_PM configuration

For Versal APU validation in Zephyr CI it is useful to run only one QEMU
instance and not model PLM (Platform Loader and Manager). That's why
im

feat(versal): add support for TFA_NO_PM configuration

For Versal APU validation in Zephyr CI it is useful to run only one QEMU
instance and not model PLM (Platform Loader and Manager). That's why
implement TFA_NO_PM compilation flag to cover it. That's why don't call
any PM initialization or communication via IPI with PLM. Flag is
aligned with implementations done in Versal NET or Versal Gen 2.

Change-Id: I0a4c4c3789f78b649e2961885c87628a599e5536
Signed-off-by: Michal Simek <michal.simek@amd.com>

show more ...

fix(versal2): fix misra rule 8.13 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.8.13:
- A pointer should point to a const-qualified type whenever
possible.
- Fix:
-

fix(versal2): fix misra rule 8.13 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.8.13:
- A pointer should point to a const-qualified type whenever
possible.
- Fix:
- Add const qualifier to pointer parameters.

Change-Id: I4572e507156de74b5f9c16a59de054ac8e497562
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal2): fix misra rule 2.5 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.2.5:
- A project should not contain unused macro declarations.
- Fix:
- Remove unused mac

fix(versal2): fix misra rule 2.5 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.2.5:
- A project should not contain unused macro declarations.
- Fix:
- Remove unused macro declarations.

Change-Id: I3645a08f3282ec06a75f6ef424fab2c5bca3aed6
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal2): fix misra rule 4.6 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 Dir 4.6:
- Typedefs that indicate size and signedness should be used in
place of the basi

fix(versal2): fix misra rule 4.6 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 Dir 4.6:
- Typedefs that indicate size and signedness should be used in
place of the basic numerical types.
- Fix:
- Replace basic numerical types with specific-width typedefs.

Change-Id: Id096937ac9998a7a2e980e0e08680db5a19f87aa
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal2): fix misra rule 8.4 violation

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.8.4:
- A compatible declaration shall be visible when an object or
function with externa

fix(versal2): fix misra rule 8.4 violation

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.8.4:
- A compatible declaration shall be visible when an object or
function with external linkage is defined.
- Fix:
- Declare pm_secure_lock as static to give it internal linkage.

Change-Id: Ie538b2382e214ee2a486259b4ecddc12082334fa
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal2): fix misra rule 18.1 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.18.1:
- A pointer resulting from arithmetic on a pointer operand shall
address an elem

fix(versal2): fix misra rule 18.1 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.18.1:
- A pointer resulting from arithmetic on a pointer operand shall
address an element of the same array as that pointer operand.
- Fix:
- Add upper bounds check before array access to prevent buffer
overrun.

Change-Id: I56e8201f2bf0de1d276d2ee009dafc73f08caf75
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal2): fix misra rule 10.4 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.10.4:
- Both operands of an operator in which the usual arithmetic
conversions are per

fix(versal2): fix misra rule 10.4 violations

Fix below MISRA violation:
- MISRA Violation: MISRA-C:2012 R.10.4:
- Both operands of an operator in which the usual arithmetic
conversions are performed shall have the same essential type
category.
- Fix:
- Make operands of the same essential type category.

Change-Id: Idf3489dee8f45a5a27bda4e4392b84510352623e
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(el3-runtime): resolve essential-type mismatch

This resolves MISRA C:2012 Rule 10.7 violation
where a composite expression involved operands of differing
essential types, causing unintended impli

fix(el3-runtime): resolve essential-type mismatch

This resolves MISRA C:2012 Rule 10.7 violation
where a composite expression involved operands of differing
essential types, causing unintended implicit conversions.

The fix ensures all operands in the expression have matching
essential types by introducing explicit casts,
preventing unsafe or inconsistent arithmetic operations.

Change-Id: If01dfe78e7a5cffc8b0efa6ac969b262e236852b
Signed-off-by: Taticharla Venkata Sai <venkatasai.taticharla@amd.com>

show more ...

fix(xilinx): limit pm_feature_check deprecation warning to once per boot

The deprecation warning in pm_feature_check() is being displayed
multiple times during boot, causing log spam.

Modify the wa

fix(xilinx): limit pm_feature_check deprecation warning to once per boot

The deprecation warning in pm_feature_check() is being displayed
multiple times during boot, causing log spam.

Modify the warning to display only once per boot session by using
a static boolean flag. This maintains the deprecation notification
while reducing log verbosity.

Change-Id: Ie2ae265b0e0b4d08c6341f1870258b970f5a1fc7
Signed-off-by: Devanshi Chauhan <Devanshi.ChauhanAlpeshbhai@amd.com>

show more ...

fix(versal-net): remove client-side code of PM_ABORT_SUSPEND

PM_ABORT_SUSPEND API is removed; client-side implementation is no
longer needed.

Change-Id: If2559ca106dbb60d761d0f8c7deeb86c1f30af16
Si

fix(versal-net): remove client-side code of PM_ABORT_SUSPEND

PM_ABORT_SUSPEND API is removed; client-side implementation is no
longer needed.

Change-Id: If2559ca106dbb60d761d0f8c7deeb86c1f30af16
Signed-off-by: Madhav Bhatt <madhav.bhatt@amd.com>

show more ...

fix(versal): remove client-side implementation of PM_ABORT_SUSPEND

PM_ABORT_SUSPEND API is removed; client-side implementation is no
longer needed.

Change-Id: I34ac563b88b98e484cf33993545c0151db936

fix(versal): remove client-side implementation of PM_ABORT_SUSPEND

PM_ABORT_SUSPEND API is removed; client-side implementation is no
longer needed.

Change-Id: I34ac563b88b98e484cf33993545c0151db9362e0
Signed-off-by: Madhav Bhatt <madhav.bhatt@amd.com>

show more ...

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 ...

fix(zynqmp): remove PM_ABORT_SUSPEND API implementation

The API is not getting called by Linux. Removing it to reduce dead
code and improve maintainability.

Change-Id: Iac7a651273401b6737c92ad26cb5

fix(zynqmp): remove PM_ABORT_SUSPEND API implementation

The API is not getting called by Linux. Removing it to reduce dead
code and improve maintainability.

Change-Id: Iac7a651273401b6737c92ad26cb5f990b512889b
Signed-off-by: Madhav Bhatt <madhav.bhatt@amd.com>

show more ...

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 ...

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 ...