- TF-A - lists.trustedfirmware.org

Process for Platform-Specific LTS Candidate Patches in TF-A

by Manish Badarkhe

Hi, I would like to share the process to follow for patches that are considered candidates for TF-A LTS branches. When submitting a patch to the TF-A `integration` branch that is expected to be backported to an LTS branch, please follow the TF-A contribution guidance and add the following tag to the commit message footer: `LTS-candidate: yes` The contribution guidance is available here: https://trustedfirmware-a.readthedocs.io/en/latest/process/contributing.htm… The `LTS-candidate: yes` tag indicates that the patch is considered relevant for backporting to applicable LTS branches. Once an LTS-candidate patch has been merged into `integration`, if the patch is relevant to a particular platform, it would be appreciated if the respective platform owner/maintainer could cherry-pick and submit the patch to the applicable LTS branch(es), adding the LTS maintainers as reviewers. The list of LTS maintainers is available here: https://trustedfirmware-a.readthedocs.io/en/latest/about/maintainers.html#l… This should help ensure that LTS-relevant changes are appropriately carried over, while allowing platform-specific backports to be handled and validated by the maintainers most familiar with those platforms. Thanks for your cooperation. Please let us know if you have any questions regarding this process. Thanks, Manish Badarkhe

12 hours, 30 minutes

1
0
0 0

Trusted Firmware-A LTS v2.14.7 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.7 is now available. This release contains the following patches: 670b014e9 fix(qti): restrict EUD register r/w to debug builds only [1] 8afa01feb fix(qti): do not map secure regions [2] 5b7e825cc fix(qti): disallow secure IO accesses from secure world callers [3] 72d0f09ed fix(qti): pull in access-control backend for mem_assign [4] ebe3bfdd3 fix(qti): harden mem_assign parameter handling [5] 329b63a1e fix(cpus): workaround for Neoverse V2 erratum 2394277 [6] 26d172be2 fix(cpus): enable Neoverse-V2 external LLC support [7] 521c2a0b8 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [8] 508e466c0 fix(cpus): workaround for C1-Pro erratum 3773617 [9] 9b42e88ad fix(build): fix misapplication of errata A53 843419 [10] 9d56fd145 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [11] 85c538676 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [12] fc7017a81 fix(cpus): add workaround for C1-Nano erratum 4497400 [13] 306b56722 docs(xlat): add erratum 3683289 comments [14] a0cf2dfba docs(cpus): add erratum 4015814 comments [15] [1] https://review.trustedfirmware.org/q/Iee82e60ef2b3182f6ebd542611d909e06339d… [2] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [3] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [4] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [5] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [6] https://review.trustedfirmware.org/q/Ib1ec35e313deddd1e19eabc1fd36968d542d7… [7] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… [8] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [9] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [10] https://review.trustedfirmware.org/q/Ifffc683c0a5253a1085e1a1c2a2203950a232… [11] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [12] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [13] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [14] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [15] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.7/change-log.html Thanks, TF-A LTS team

12 hours, 49 minutes

1
0
0 0

Trusted Firmware-A LTS v2.12.15 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.15 is now available. This release contains the following patches: fc6a2cbd5 fix(cpus): workaround for C1-Pro erratum 3773617 [1] 9126701a2 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [2] 61553a9a2 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [3] 0e52b50b2 fix(cpus): add workaround for C1-Nano erratum 4497400 [4] 3ec9c78b0 fix(docs): fix some broken links [5] 789ffc7b3 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [6] a1e77604d docs(xlat): add erratum 3683289 comments [7] 8412c2855 docs(cpus): add erratum 4015814 comments [8] 8022db055 fix(xilinx): enforce volatile call status vars [9] 326307098 fix(el3-spmc): prevent integer overflow in memory overlap validation [10] 9cb9d6fed fix(guid-partition): harden backup GPT loading [11] ce1185549 build(deps): bump igraph from 0.11.6 to 0.11.8 in /tools/cot_dt2c [12] ed3c5dda3 build(deps-dev): bump pytest from 8.3.4 to 8.3.5 in /tools/cot_dt2c [13] fd5e53f8f build(deps-dev): bump pytest from 8.3.3 to 8.3.5 in /tools/tlc [14] 8c33e76ba build(deps-dev): bump bandit from 1.7.9 to 1.7.10 in /tools/tlc [15] ad69789cf build(deps): bump tox from 4.20.0 to 4.25.0 in /tools/tlc [16] d2eb457b2 build(deps-dev): bump commitizen [17] [1] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [2] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [3] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [4] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [5] https://review.trustedfirmware.org/q/I384094c8dcf3e93875c9052afa79ad826b990… [6] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [7] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [8] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… [9] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… [10] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [11] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [12] https://review.trustedfirmware.org/q/Icdff20c79e80d2e28243238465aa0a82aea86… [13] https://review.trustedfirmware.org/q/Ic00e1f7f3eed0c15efa4aad2be5d65d9b0c03… [14] https://review.trustedfirmware.org/q/I7ca2856751eb8de70042b4626581ee1d028a8… [15] https://review.trustedfirmware.org/q/Ied911c87232dde44eccde745a3e8c8ef9784d… [16] https://review.trustedfirmware.org/q/I2301600ad946368ad6cabec6badd752ab0fec… [17] https://review.trustedfirmware.org/q/Ib18c0496ce0dae554509ec80247da0a630f15… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.15/change-log.html Thanks, TF-A LTS team

13 hours, 11 minutes

1
0
0 0

Trusted Firmware-A LTS v2.8.46 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.46 is now available. This release contains the following patches: 1a52c0761 fix(intel): update fcs crypto init code to check for mode [1] fc38a9df1 fix(tools): change data type to size_t for doimage [2] e576443dd fix(imx8m): don't reconfigure default region0 [3] b741ab045 fix(el3-spmc): prevent integer overflow in memory overlap validation [4] 8efc140e0 fix(guid-partition): harden backup GPT loading [5] 4c689a4d7 fix(xilinx): enforce volatile call status vars [6] [1] https://review.trustedfirmware.org/q/I702ce90e229188830f8936bee2999610e9559… [2] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [3] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [4] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [5] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [6] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.46/change-log.html Thanks, TF-A LTS team

18 hours, 20 minutes

1
0
0 0

Trusted Firmware-A LTS v2.10.34 Release Announcement

by svc_openci_enginfra＠arm.com

1 week

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Sep 3, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic this week. Thanks & Regards, Olivier. " TF-A Tech Forum Thursday Sep 3, 2026 ⋅ 5pm – 6pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Trusted Firmware is inviting you to a scheduled Zoom meeting. Topic: TF-A Tech Forum Time: May 15, 2025 02:00 PM London Every 2 weeks on Thu, 78 occurrence(s) Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics… Join Zoom Meeting https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… Meeting ID: 935 5786 3987 Passcode: 939141 --- One tap mobile +12532158782,,93557863987# US (Tacoma) +13017158592,,93557863987# US (Washington DC) --- Dial by your location • +1 253 215 8782 US (Tacoma) • +1 301 715 8592 US (Washington DC) • +1 305 224 1968 US • +1 309 205 3325 US • +1 312 626 6799 US (Chicago) • +1 346 248 7799 US (Houston) • +1 360 209 5623 US • +1 386 347 5053 US • +1 507 473 4847 US • +1 564 217 2000 US • +1 646 558 8656 US (New York) • +1 646 931 3860 US • +1 669 444 9171 US • +1 669 900 9128 US (San Jose) • +1 689 278 1000 US • +1 719 359 4580 US • +1 253 205 0468 US • 833 548 0276 US Toll-free • 833 548 0282 US Toll-free • 833 928 4608 US Toll-free • 833 928 4609 US Toll-free • 833 928 4610 US Toll-free • 877 853 5247 US Toll-free • 888 788 0099 US Toll-free Meeting ID: 935 5786 3987 Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 week, 1 day

1
0
0 0

Deprecation notification of Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms

by Boyan Karatotev

Hello, During a recent code ownership cleanup we have identified three platforms that lack designated code owners: Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms. All three have not had any significant activity for some time now and as such we are going to mark them as deprecated. The patches to do that are here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/53842. We will go ahead with them in the next week or so unless we hear any objections. These platforms will not be removed until after the next v2.16 release scheduled for later this year. We will not proceed with removal if code owners are found before then. Thanks, Boyan

2 weeks, 3 days

1
0
0 0

SDEI: SDEI_EVENT_0 trigger dropped while PE masked — by design?

by wtliang785

Hi all, I'd like to ask whether the following behavior of SDEI_EVENT_0 is intended, and whether it's a known limitation of the SDEI + GIC SGI semantics. I've read the code carefully but want to confirm the intent before relying on or working around it. ## Setup - TF-A SDEI, event 0 is a "signalable" private event whose backing interrupt is a Secure SGI (on our platform, SGI 9). - include/services/sdei.h, SDEI_DEFINE_EVENT_0(_intr) -> SDEI_PRIVATE_EVENT(SDEI_EVENT_0, _intr, SDEI_MAPF_SIGNALABLE) - services/std_svc/sdei/sdei_main.c: asserts event 0 must be a Secure SGI and may only carry SIGNALABLE|PRIVATE. ## What I observe in code When the PE is SDEI-masked (client called SDEI_PE_MASK) and the SGI backing event 0 fires, the handler does *not* preserve the trigger: 1. The EL3 FIQ is taken and acked in bl31/ehf.c ehf_el3_interrupt_handler() via plat_ic_acknowledge_interrupt() (reads ICC_IAR — interrupt now Active, its Pending bit consumed). 2. It reaches sdei_intr_handler() (services/std_svc/sdei/sdei_intr_mgmt.c). At L463, state->pe_masked is true, so it calls handle_masked_trigger() and returns 0. 3. handle_masked_trigger() : /* Nothing to do for event 0 */ if (map->ev_num == SDEI_EVENT_0) return; i.e. for event 0 it does none of the "freeze for replay" steps that a normal private event takes : plat_ic_disable_interrupt(intr); plat_ic_set_interrupt_pending(intr); plat_ic_end_of_interrupt(intr_raw); state->pending_enables = true; So while the PE is masked, an event-0 trigger is acknowledged and then silently dropped, with nothing stored for replay on the next SDEI_PE_UNMASK. ## Why I think this happens (and want to confirm) The "freeze for replay" mechanism for normal private events relies on re-asserting Pending via plat_ic_set_interrupt_pending(), because the ack already consumed the Pending bit. But for an SGI this is not permitted — plat/common/plat_gicv3.c: asserts it out: void plat_ic_set_interrupt_pending(unsigned int id) { /* Disallow setting SGIs pending */ assert(id >= MIN_PPI_ID); gicv3_set_interrupt_pending(id, plat_my_core_pos()); } So event 0 (backed by an SGI) cannot have its Pending bit re-asserted in software, which is consistent with the "Nothing to do for event 0" early return. Combined with the level/merge semantics of GIC SGIs (a sender firing the same SGI N times is represented as a single Pending, not a count), this means a masked-PE client can at most learn "an event happened while masked", never how many or which — by design. ## My questions 1. Is dropping an event-0 trigger while the PE is masked the intended behaviour (a consequence of "event 0 is a signalable SGI, counting is not guaranteed"), rather than a bug? The "Nothing to do for event 0" comment reads as deliberate, but I'd like explicit confirmation. 2. Is the recommended mitigation simply to avoid firing event 0 while the PE is masked (buffer on the sender side, deliver after unmask), or to use a normal explicit event for anything requiring precise accounting? Or is there a platform hook intended for this case that I'm missing (e.g. plat_sdei_handle_masked_trigger — though that path is only taken for shared ANY-PE events , not event 0)? 3. Separately (not the focus of this question): on this masked path neither handle_masked_trigger() nor sdei_intr_handler() calls plat_ic_end_of_interrupt() for event 0, and neither the EHF top-level handler nor the runtime_exceptions.S dispatch macro performs a fallback EOI. So the acked SGI appears to be left Active with no EOI on this path. Is there a later EOI for this SGI that I've missed, or is that also expected here? I don't want to conflate this with the "drop" question above; I'm just flagging it. For reference, this is on an in-tree SDEI path; the platform only defines event 0 via SDEI_DEFINE_EVENT_0(PLAT_SDEI_SGI_PRIVATE) and does not modify handle_masked_trigger(). Thanks, Tianliang

3 weeks, 1 day

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Aug 20, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Also cancelling Aug 20th instance as no topic and expected low attendance." TF-A Tech Forum Thursday Aug 20, 2026 ⋅ 5pm – 6pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumTime: May 15, 2025 02:00 PM London Every 2 weeks on Thu, 78 occurrence(s)Please download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics… Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 939141---One tap mobile+12532158782,,93557863987# US (Tacoma)+13017158592,,93557863987# US (Washington DC)---Dial by your location• +1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 669 444 9171 US• +1 669 900 9128 US (San Jose)• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US• 833 548 0276 US Toll-free• 833 548 0282 US Toll-free• 833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 month

1
0
0 0

Canceled event with note: TF-A Tech Forum @ Thu Aug 6, 2026 5pm - 6pm (GMT+2) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Hi Cancelling as topic on Aug 6th. Regards, Olivier. " TF-A Tech Forum Thursday Aug 6, 2026 ⋅ 5pm – 6pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumTime: May 15, 2025 02:00 PM London Every 2 weeks on Thu, 78 occurrence(s)Please download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics… Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 939141---One tap mobile+12532158782,,93557863987# US (Tacoma)+13017158592,,93557863987# US (Washington DC)---Dial by your location• +1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 669 444 9171 US• +1 669 900 9128 US (San Jose)• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US• 833 548 0276 US Toll-free• 833 548 0282 US Toll-free• 833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 month

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A