docs(juno): update PSCI instrumentation data

Update for v2.14 release based on v2.14-rc0

Change-Id: Id0cf75e284cc02a513d134ccd550fe9a73ac6909
Signed-off-by: Xialin Liu <xialin.liu@arm.com>

fix: remove circular dependency on ENABLE_FEAT_RAS

ENABLE_FEAT_RAS is enabled by arch_features.mk based on the value of
ARM_ARCH_{MAJOR, MINOR}, but that is only called after each platform's
platfor

fix: remove circular dependency on ENABLE_FEAT_RAS

ENABLE_FEAT_RAS is enabled by arch_features.mk based on the value of
ARM_ARCH_{MAJOR, MINOR}, but that is only called after each platform's
platform.mk. That makes a circular dependency when a file needs to be
compiled based on the flag's value.

Well, FEAT_RAS is mandatory from v8.2 and platforms that set
ARM_ARCH_{MAJOR, MINOR} such need not check for its presence - it will
be present. So remove the check to remove the dependency.

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

show more ...

feat(cpus): add support for LSC25 E-core CPU

Add basic CPU library code to support the Large Screen Compute 2025
E-core CPU.

Change-Id: Ibda2e8441d3a3e35941448b483d07e17db2ef234
Signed-off-by: Ryan

feat(cpus): add support for LSC25 E-core CPU

Add basic CPU library code to support the Large Screen Compute 2025
E-core CPU.

Change-Id: Ibda2e8441d3a3e35941448b483d07e17db2ef234
Signed-off-by: Ryan Everett <ryan.everett@arm.com>
Signed-off-by: Aditya Deshpande <aditya.deshpande@arm.com>

show more ...

feat(cpus): add support for LSC25 P-core CPU

Add basic CPU library code to support the Large Screen Compute 2025
P-core CPU.

Change-Id: Icfd2fdbaed577e64cb2db028416a6eca5ba2cfcf
Signed-off-by: Ryan

feat(cpus): add support for LSC25 P-core CPU

Add basic CPU library code to support the Large Screen Compute 2025
P-core CPU.

Change-Id: Icfd2fdbaed577e64cb2db028416a6eca5ba2cfcf
Signed-off-by: Ryan Everett <ryan.everett@arm.com>
Signed-off-by: Aditya Deshpande <aditya.deshpande@arm.com>

show more ...

build(dev-deps): bump js-yaml in the dev-deps group across 1 directory

Bumps the dev-deps group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` fr

build(dev-deps): bump js-yaml in the dev-deps group across 1 directory

Bumps the dev-deps group with 1 update in the / directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `js-yaml` from 4.1.0 to 4.1.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](https://github.com/nodeca/js-yaml/compare/4.1.0...4.1.1)

--
updated-dependencies:
- dependency-name: js-yaml
dependency-version: 4.1.1
dependency-type: direct:development
update-type: version-update:semver-patch
dependency-group: dev-deps
...

Change-Id: I3835eeb260fb482ea812eb96d95059a71dd3392e
Signed-off-by: dependabot[bot] <support@github.com>

show more ...

feat(fvp): load SP_PKGs with TRANSFER_LIST

To enable loading of SP_PKGs when using the TRANSFER_LIST build option,
this patch loads TB_FW_CONFIG in BL1 and populates sp_mem_params_descs
in arm_trans

feat(fvp): load SP_PKGs with TRANSFER_LIST

To enable loading of SP_PKGs when using the TRANSFER_LIST build option,
this patch loads TB_FW_CONFIG in BL1 and populates sp_mem_params_descs
in arm_transfer_list_dyn_cfg_init().

Since there is no standard tag_id defined for TB_FW_CONFIG in the
transfer list, define PLAT_ARM_TB_FW_CONFIG_TL_TAG as a platform-specific
identifier to load TB_FW_CONFIG.

With this change, BL2 can load the SP_PKGs specified in TB_FW_CONFIG.

Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
Change-Id: I2470c1ef3bf2bf921d0de1fff541565df13eaee4

show more ...

Merge "docs(ff-a): document `sri-interrupts-policy` field" into integration

fix(allwinner): avoid crash when running without DTB

For determining the PMIC type and the bus its connected to, we use the
DTB that is appended to the U-Boot binary, by looking for it in DRAM.
And

fix(allwinner): avoid crash when running without DTB

For determining the PMIC type and the bus its connected to, we use the
DTB that is appended to the U-Boot binary, by looking for it in DRAM.
And while we bail out correctly if we don't find it there, we later try
to use the DTB pointer - without checking.

Add a check in sunxi_pmic_setup(), to only proceed if we have found a
DTB before, and exit early otherwise.

This fixes more experimental setups, where TF-A is run without U-Boot.

Change-Id: I9a7677be057a84fe6bee093d098be758970eec81
Signed-off-by: Andre Przywara <andre.przywara@arm.com>

show more ...

docs(ff-a): document `sri-interrupts-policy` field

Add the encoding information for the `sri-interrupts-policy` field
for SP FF-A manifest.

Signed-off-by: J-Alves <joao.alves@arm.com>
Change-Id: Ib

docs(ff-a): document `sri-interrupts-policy` field

Add the encoding information for the `sri-interrupts-policy` field
for SP FF-A manifest.

Signed-off-by: J-Alves <joao.alves@arm.com>
Change-Id: Ib8f6a3ba02be3a312abd1f8ab4a75874290a244f

show more ...

fix(intel): remove invalid SDM SMMU Stream ID register from bypass list

The register is SDM-owned and not accessible by HPS.
It was added by mistakein v2.7.0.
Removing it ensures correct access cont

fix(intel): remove invalid SDM SMMU Stream ID register from bypass list

The register is SDM-owned and not accessible by HPS.
It was added by mistakein v2.7.0.
Removing it ensures correct access control.

Change-Id: I76d27e5b53bfb115ace6011dbb79f2fac049bb4e
Signed-off-by: Jit Loon Lim <jit.loon.lim@altera.com>

show more ...

fix(intel): prevent invalid register rejection on non-A5F4 devices

Move TSN_TBU_STREAM_CTRL_REG_3_TSN0/1/2 handling outside the
main switch to ensure non-A5F4 devices (e.g., A5F0) evaluate
other val

fix(intel): prevent invalid register rejection on non-A5F4 devices

Move TSN_TBU_STREAM_CTRL_REG_3_TSN0/1/2 handling outside the
main switch to ensure non-A5F4 devices (e.g., A5F0) evaluate
other valid registers.

Previously, TSN cases were inside the switch and followed
by a `break` if not A5F4, causing early exit and -1 return.
Valid registers (e.g., ECC_INTMASK_x)were rejected, blocking boot.

Now, A5F4 TSN registers are handled conditionally
and fallthrough is clean for all other devices.

Change-Id: I1339e0e3951ccb68f02dc437f25db6c27d2a0877
Signed-off-by: Jit Loon Lim <jit.loon.lim@altera.com>

show more ...

fix(intel): allow kernel access to TSN TBU stream control registers

Added TSN_TBU_STREAM_CTRL_REG_3_TSN0/1/2 to ATF's secure range check
to permit setting the 31st bit from kernel space.

Change-Id:

fix(intel): allow kernel access to TSN TBU stream control registers

Added TSN_TBU_STREAM_CTRL_REG_3_TSN0/1/2 to ATF's secure range check
to permit setting the 31st bit from kernel space.

Change-Id: I74bd296c4c050fb61d4df5c1bd5b57449b3a13e3
Signed-off-by: Jit Loon Lim <jit.loon.lim@altera.com>

show more ...

docs: describe RAS KFH limitations and its mitigation in future

Signed-off-by: Manish Pandey <manish.pandey2@arm.com>
Change-Id: I27b739413140fc310b2bcb3a0812e07ba29e36d8

fix(libfdt): fix coverity reported issue

Check for null pointer before usage of prop.

Coverity Reports -
CID 394590: (#1 of 1): Dereference null return value (NULL_RETURNS)
6. dereference: Derefere

fix(libfdt): fix coverity reported issue

Check for null pointer before usage of prop.

Coverity Reports -
CID 394590: (#1 of 1): Dereference null return value (NULL_RETURNS)
6. dereference: Dereferencing a pointer that might be NULL prop when
calling fdt_setprop.

Change-Id: I2f864a1b476ef4a22f34d8157e1176354b996172
Signed-off-by: Govindraj Raja <govindraj.raja@arm.com>

show more ...

fix(libc): fix coverity deadcode issue

Comparison checks makes no sense due to the way libc
in TF-A has implemeneted long and long long which are the same
so checking for overflow is deadcode.

Cove

fix(libc): fix coverity deadcode issue

Comparison checks makes no sense due to the way libc
in TF-A has implemeneted long and long long which are the same
so checking for overflow is deadcode.

Coverity reports -
CID 493664: (#1 of 1): Logically dead code (DEADCODE)

The cutoff and cutlim check is good enough to avoid any overflow.
So remove overflow checks added.

Change-Id: I83e4197e5107bf7c5edc8050bc831b721454573b
Signed-off-by: Govindraj Raja <govindraj.raja@arm.com>

show more ...

fix(zlib): fix overflow issue from coverity

Fix the overflow when m equals 0 in the multmodp function during the
for loop. As identified by coverity report.

Reported as -

CID 427579: (#1 of 1): Ov

fix(zlib): fix overflow issue from coverity

Fix the overflow when m equals 0 in the multmodp function during the
for loop. As identified by coverity report.

Reported as -

CID 427579: (#1 of 1): Overflowed constant (INTEGER_OVERFLOW)
163. overflow_const: Expression m - 1UL, where m is known to be equal
to 0, underflows the type of m - 1UL, which is type unsigned long.

Change-Id: Idb0238bc8c7ff11f1fc22f4b69deef3d3ed4acb6
Signed-off-by: Govindraj Raja <govindraj.raja@arm.com>

show more ...

Merge changes from topic "fix-windows-builds" into integration

* changes:
fix(build): shell-escape toolchain wrapper commands
fix(build): fix incorrect parentheses expansion in `shell-map`

fix(build): shell-escape toolchain wrapper commands

When we split toolchain tool commands into their wrapper and program
shell fragments, we do so by iterating over each shell word and
forwarding it

fix(build): shell-escape toolchain wrapper commands

When we split toolchain tool commands into their wrapper and program
shell fragments, we do so by iterating over each shell word and
forwarding it to `toolchain-guess-tool`.

However, we receive each word in its raw form, but we pass it to a
function which expects a fragment. If the raw word contains characters
which are syntactically-meaningful to the shell, then the command can
misbehave, and the build system can unwittingly do some funky things.

This small change just ensures that we re-quote the shell word we
receive before forwarding it on.

Change-Id: I325e1c135fee97d749da927c08e181775b14d146
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

fix(build): fix incorrect parentheses expansion in `shell-map`

The previous commit which attempted to fix the expansions in `shell-map`
doubled up on the dollar signs for all of the escape substitut

fix(build): fix incorrect parentheses expansion in `shell-map`

The previous commit which attempted to fix the expansions in `shell-map`
doubled up on the dollar signs for all of the escape substitutions; this
"fixed" the Windows build.

However, the expansion of the parentheses is actually still wrong.
Consider the following example:

print = $(warning $(1))

$(call shell-map,print,'$$' '$(lparen)' '$(rparen)')

... which prints:

make_helpers/utilities.mk:620: $
make_helpers/utilities.mk:620: ${lparen}
make_helpers/utilities.mk:620: ${rparen}

However, what we expect to see is:

make_helpers/utilities.mk:620: $
make_helpers/utilities.mk:620: (
make_helpers/utilities.mk:620: )

The reason we do these substitutions is because, behind the scenes, the
function generates a small snippet of Make which calls the map function
provided by the user. To do that safely, we need to escape characters
which can cause premature expansion (`$`), and any characters which can
interfere with the syntax of the `call` function (`(` and `)`).

The shell snippet that we *expected* the example above to generate was:

$(call print,$$,1)
$(call print,${lparen},2)
$(call print,${rparen},3)

However, as of the last "fix", what it is actually generating is:

$(call print,$$,1)
$(call print,$${lparen},2)
$(call print,$${rparen},3)

This breaks the Windows build again but that's because this bug was
actually three bugs from the start.

Change-Id: Ibaf044806101334ddf4080df8da18f9aac8667e5
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

Merge "fix(build): fix incorrect expansions in `shell-map`" into integration

Merge "fix(fvp): use global option for setting PLAT_ARM_MAX_BL2_SIZE" into integration

fix(fvp): use global option for setting PLAT_ARM_MAX_BL2_SIZE

Use global option TRUSTED_BOARD_BOOT for setting PLAT_ARM_MAX_BL2_SIZE.

Change-Id: Ia360b36535d2039de8e41da90dd4c8478adb6d54
Signed-off

fix(fvp): use global option for setting PLAT_ARM_MAX_BL2_SIZE

Use global option TRUSTED_BOARD_BOOT for setting PLAT_ARM_MAX_BL2_SIZE.

Change-Id: Ia360b36535d2039de8e41da90dd4c8478adb6d54
Signed-off-by: Manish V Badarkhe <Manish.Badarkhe@arm.com>

show more ...

Merge "chore(fvp): bump maximum permitted Trusted SRAM size" into integration

Merge "fix(versal2): align comment about invalid console selection" into integration

chore(fvp): bump maximum permitted Trusted SRAM size

Bump the size of the Trusted SRAM in FVP builds, as we are now exceeding
the 256KB limit in a meaningful number of builds.

Change-Id: Iefd584172

chore(fvp): bump maximum permitted Trusted SRAM size

Bump the size of the Trusted SRAM in FVP builds, as we are now exceeding
the 256KB limit in a meaningful number of builds.

Change-Id: Iefd58417297507eaa9b24e55fc36de67bd16b716
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...