On 11/5/26 10:23 PM, Tom Rini wrote:
On Thu, Nov 05, 2026 at 09:03:55PM +0100, Marek Vasut wrote:
On 11/5/26 8:41 PM, Tom Rini wrote:
On Thu, Nov 05, 2026 at 08:10:26PM +0100, Marek Vasut wrote:
On 11/5/26 7:51 PM, Massimo Pegorer wrote:
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:
u-boot$ git log --oneline HEAD~4..
1e29311663e (HEAD -> master) Revert "remoteproc: Hide REMOTEPROC options in
REMOTEPROC conditional"
97162e533ca remoteproc: Hide REMOTEPROC options in REMOTEPROC conditional
df3b8e16e6d remoteproc: Make REMOTEPROC_MAX_FW_SIZE depend on REMOTEPROC
d1d45c926a5 (origin/main) Merge branch 'main' of
https://git.u-boot-project.org/u-boot/custodians/u-boot-riscv
Wait, your new patch didn't just replace the old patch?
Nope, it is two patches now, simple clean up one, and more extensive change
one.
Alright. I can't reproduce my failure either. That said, should I just
squash these two patches together, along with adding the fix for the
newly added TI rproc option and post v2, or do you want to? Thanks.
Nope, keep them separate please, they were intended as a simple fix and
larger rework. In case the later breaks something, it could be reverted
separately too. Thank you.