linux/meta-ti.git, branch 11.01.07

CI/CD Auto-Merger: cicd.scarthgap.202507231325

2025-07-23T18:25:46+00:00

Updated the value(s) for: ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=604d03d4f20727f5f9173d7db1e427cfbdd17022..f59a711599249ecac75fea38b7a15ef9137d650d u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c199d231a1477137f1b04e794e309af1eeb4c3dd..3bcfad6cee95403f7f62dd9d871cc3ea948c0761 k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=b537524cde12bf24a799f6b087b1bc6263bad87d..6034420195cf763c9470fb2113810695e5e37a23 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=36c7ff7f60e71677601505976d915286923be488..b5ee9420d81f46861c4f0a172154e477feda1980 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=e6ed2862fe19bd0c8901ecfaa15a3805209d40bd..72f48d59b8f087fa0dd1f1e8c2c0b5bc0baa537c Signed-off-by: LCPD Automation Script

ti-kernel-devicetree-prefix: use shared kernel sources for prefix match

2025-07-23T13:48:29+00:00

Handle devicetree prefix matching inside the shared kernel sources tree, instead of ${S}. From the kernel recipe perspective, ${S} is just a symlink to the shared kernel sources. But since the new FIT image wrapper is a separate recipe now, it has its own different ${S}. To enable FIT image wrapper to support devicetree prefix matching, it also needs to access the same shared kernel sources. Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

beagle-bsp: unset KERNEL_DEVICETREE_PREFIX

2025-07-23T13:48:29+00:00

Beagle machines define both static KERNEL_DEVICETREE list and dynamic KERNEL_DEVICETREE_PREFIX matching. But BB.org kernel recipes only use the static list, while TI kernel recipes use dynamic prefix matching by default. Since devicetree lists now need to be used outside of the kernel build, specifically for the new FIT processing wrapper, explicitly unset KERNEL_DEVICETREE_PREFIX to disable dynamic devicetree prefix matching, when BB.org BSPs are selected. This way both kernel build and FIT image wrapper will have the same list of DTBs to handle, based on the BSP selection. Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

CI/CD Auto-Merger: cicd.scarthgap.202507171300

2025-07-17T18:00:35+00:00

Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=373c2f5646e3947b3b4a340da729288ee3f07833..604d03d4f20727f5f9173d7db1e427cfbdd17022 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=827c35b4d141865e25d234e3d298614e6c47150c..c199d231a1477137f1b04e794e309af1eeb4c3dd k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=e6abc1b87f1d5bc4c2ab5f1ebfbf5a70e437dcb4..b537524cde12bf24a799f6b087b1bc6263bad87d linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f0e4f5ca0905956c70779b31663f594c08c6a3bc..36c7ff7f60e71677601505976d915286923be488 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=78e6abff322081d53c5a685d927476086c9b2846..e6ed2862fe19bd0c8901ecfaa15a3805209d40bd Signed-off-by: LCPD Automation Script

linux-ti-staging-rt_6.12: Need finer control for BRANCH

2025-07-14T19:49:22+00:00

The CICD flow needs to control the value for BRANCH in order to have the recipe updated with the next SRCREV, but point to the CICD/next branch for initial build/test. With this split in linux-ti-staging-rt we cannot just have an override for BRANCH in the local.conf because it trumps the new BRANCH_ARM32 system. This patch creates an additional "default" variable BRANCH_ARM64 (or not arm32), which can be controlled separately by the CICD flow. Then BRANCH simply is picking between the two and so can be controlled by overrides in the recipe. Signed-off-by: Ryan Eatmon

linux-ti-staging-rt_6.12: Add PV tracking for ARM32

2025-07-12T16:31:30+00:00

Since the kernel branches could theoretically drift apart, we need to track the PV of the kernel on the RT branch for the ARM32 platforms as well. Signed-off-by: Ryan Eatmon

u-boot-ti-mainline: Update to version: v2025.07

2025-07-11T18:33:44+00:00

Updated the value(s) for: u-boot-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script Signed-off-by: Ryan Eatmon

ti-librpmsg-dma: mark it as compatible with K3 platforms

2025-07-11T17:37:02+00:00

As ti-librpmsg-dma depends on ti-rpmsg-char, which is only compatible with K3 platforms, ti-librpmsg-dma should also have the same limitations. This resolves yocto-check-layer failure: ERROR: Nothing PROVIDES 'ti-rpmsg-char' (but .../ti-librpmsg-dma_1.0.bb DEPENDS on or otherwise requires it) ti-rpmsg-char was skipped: incompatible with machine qemux86-64 (not in COMPATIBLE_MACHINE) Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

linux-ti-staging-rt_6.12: Add ARM32 RT branch

2025-07-11T17:36:42+00:00

While all ARM64 devices use the same branch for RT and non-RT builds, the ARM32 devices have a separate branch for RT Kernel which is "ti-rt-linux-6.12.y-arm32". Update the BRANCH and SRCREV for ARM32 devices for RT builds. Signed-off-by: Beleswar Padhi Signed-off-by: Ryan Eatmon

meta-ti-bsp: u-boot: change tispl_falcon to tifalcon

2025-07-10T16:26:56+00:00

The payload containing ATF, OP-TEE and DM in falcon mode was renamed from 'tispl_falcon.bin' to 'tifalcon.bin' when adapting upstream patches to ti-u-boot[1]. Therefore this patch fixes the same in meta-ti. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/configs/k3_r5_falcon.config?h=ti-u-boot-2025.01-next#n36 Signed-off-by: Anshul Dalal Signed-off-by: Ryan Eatmon