On Thu, Nov 05, 2026 at 07:25:05PM +0100, Marek Vasut wrote: > On 11/5/26 3:42 PM, Tom Rini wrote: > > On Wed, Nov 04, 2026 at 06:33:21PM +0100, Marek Vasut wrote: > > > On 11/4/26 3:29 PM, Tom Rini wrote: > > > > On Mon, Oct 26, 2026 at 11:11:32PM +0100, Marek Vasut wrote: > > > > > > > > > Add conditional around REMOTEPROC menu entries, turn REMOTEPROC into > > > > > configurable boolean, and update all defconfigs and Kconfigs which > > > > > previously only selected REMOTEPROC driver to also select REMOTEPROC > > > > > itself. > > > > > > > > > > Signed-off-by: Marek Vasut <[email protected]> > > > > > --- > > > > > Cc: Massimo Pegorer <[email protected]> > > > > > Cc: MD Danish Anwar <[email protected]> > > > > > Cc: Tom Rini <[email protected]> > > > > > Cc: [email protected] > > > > > > > > Unfortunately this misses some handful of at least TI K3 platforms. I > > > > think using qconfig.py to confirm which configs have REMOTEPROC set > > > > before / after, and that they match would make sorting that part of the > > > > problem out easier. Do you have time to do that, or should I pick it up > > > > and do a v2? Thanks. > > > I can respin this, but do you know which platforms got missed ? > > > > I lost the list, sorry. It was a number of the r5 builds. Perhaps some > > fragment got missed? But qconfig.py -f REMOTEPROC, with a db built with > > and without the patch will quickly show which oens it is. > I have this in either case: > > am6254atl_evm_a53 am6254atl_evm_r5 am62_pocketbeagle2_a53 > am62_pocketbeagle2_r5 am62ax_evm_a53 am62ax_evm_a53_ethboot am62ax_evm_r5 > am62ax_evm_r5_ethboot am62dx_evm_a53 am62dx_evm_r5 am62px_evm_a53 > am62px_evm_a53_ethboot am62px_evm_r5 am62px_evm_r5_ethboot > am62x_beagleplay_a53 am62x_beagleplay_r5 am62x_evm_a53 am62x_evm_a53_ethboot > am62x_evm_r5 am62x_evm_r5_ethboot am62x_lpsk_a53 am62x_lpsk_r5 am64x_evm_a53 > am64x_evm_r5 am65x_evm_a53 am65x_evm_r5 am65x_evm_r5_usbdfu > am65x_evm_r5_usbmsc am67a_beagley_ai_a53 am67a_beagley_ai_r5 am68_sk_a72 > am68_sk_a72_ethboot am68_sk_r5 am68_sk_r5_ethboot am69_sk_a72 > am69_sk_a72_ethboot am69_sk_r5 am69_sk_r5_ethboot aquila-am69_a72 > aquila-am69_r5 aquila-imx95 imx8mm_evk imx8mm_evk_fspi imx8mn_ddr4_evk > imx8mn_evk imx8mp_evk imx8mq_evk imx93_11x11_evk imx93_9x9_qsb > imx93_9x9_qsb_inline_ecc imx93_frdm imx93w_evk imx93w_evk_inline_ecc > imx95_15x15_evk imx95_15x15_frdm imx95_19x19_evk imx95_19x19_frdm_pro > imx95_a0_19x19_evk imx95_navq iot2050 j7200_evm_r5 j721e_beagleboneai64_a72 > j721e_beagleboneai64_r5 j721e_evm_a72 j721e_evm_r5 j721e_sk_a72 j721e_sk_r5 > j721s2_evm_a72 j721s2_evm_r5 j722s_evm_a53 j722s_evm_a53_ethboot > j722s_evm_r5 j722s_evm_r5_ethboot j742s2_evm_a72 j742s2_evm_r5 > j784s4_evm_a72 j784s4_evm_r5 k2g_evm k2g_hs_evm phycore_am62ax_a53 > phycore_am62ax_r5 phycore_am62ax_r5_ethboot phycore_am62ax_r5_usbdfu > phycore_am62x_a53 phycore_am62x_r5 phycore_am62x_r5_ethboot > phycore_am62x_r5_usbdfu phycore_am64x_a53 phycore_am64x_r5 phycore_am68x_a72 > phycore_am68x_r5 r8a779g0_whitehawk r8a779g3_sparrowhawk > r8a78000_ironhide_cm33 sandbox64 sandbox64_lwip sandbox sandbox_flattree > sandbox_nocmdline sandbox_noinst sandbox_spl sandbox_vpl sc598-som-ezkit-spl > sc598-som-ezlite-spl stm32mp15-icore-stm32mp1-ctouch2 > stm32mp15-icore-stm32mp1-edimm2.2 stm32mp15-microgea-stm32mp1-microdev2-of7 > stm32mp15-microgea-stm32mp1-microdev2 stm32mp15-odyssey stm32mp15_basic > stm32mp15 stm32mp15_dhcom_basic stm32mp15_dhcom_drc02_basic > stm32mp15_dhcom_pdk2_basic stm32mp15_dhcom_picoitx_basic > stm32mp15_dhcor_avenger96_basic stm32mp15_dhcor_basic > stm32mp15_dhcor_drc_compact_basic stm32mp15_dhcor_testbench_basic > stm32mp15_trusted toradex-smarc-imx95 verdin-am62_a53 verdin-am62_r5 > verdin-am62p_a53 verdin-am62p_r5 verdin-imx95 > > Do you also have this patch applied? > > [PATCH] remoteproc: Make REMOTEPROC_MAX_FW_SIZE depend on REMOTEPROC
No, because I thought this patch replaced the other patch, sigh, sorry for the confusion. -- Tom
signature.asc
Description: PGP signature
