Hi, Il giorno gio 5 nov 2026 alle ore 15:42 Tom Rini <[email protected]> ha scritto: > > 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.
This is the result of comparing the two qoconfig.py outputs: am65x_evm_a53 am68_sk_a72 am68_sk_a72_ethboot am69_sk_a72 am69_sk_a72_ethboot aquila-am69_a72 imx95_15x15_frdm imx95_19x19_frdm_pro iot2050 j721e_beagleboneai64_a72 j721e_evm_a72 j721e_sk_a72 j721s2_evm_a72 j742s2_evm_a72 j784s4_evm_a72 (I had to drop also the select REMOTEPROC for the new REMOTEPROC_TI_K3_HSM_M4F which landed into main but not yet included in the patch) Could adding an "imply REMOTEPROC" in arch/arm/mach-k3/Kconfig, where other REMOTEPROC sub-options are implied, help to simplify? Avoid need to add it to defconfigs. Regards, Massimo > > -- > Tom
