On Fri, Aug 29, 2025 at 08:56:52AM -0600, Tom Rini wrote: > On Fri, Aug 29, 2025 at 09:32:00AM -0500, Andrew Davis wrote: > > On 8/29/25 12:34 AM, Beleswar Padhi wrote: > > > This reverts commit 548ae9d1a537464254afac63f802179a24c645d6. > > > > > > The IPU remote processor is only present in TI OMAP SoCs. Remove the > > > ARCH_K3 dependency from Kconfig. This driver builds just fine without > > > ARCH_K3 config. > > > > > > Signed-off-by: Beleswar Padhi <b-pa...@ti.com> > > > --- > > > drivers/remoteproc/Kconfig | 1 - > > > 1 file changed, 1 deletion(-) > > > > > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig > > > index e9f19a69433..a3ecea05e20 100644 > > > --- a/drivers/remoteproc/Kconfig > > > +++ b/drivers/remoteproc/Kconfig > > > @@ -125,7 +125,6 @@ config REMOTEPROC_TI_PRU > > > config REMOTEPROC_TI_IPU > > > bool "Support for TI's K3 based IPU remoteproc driver" > > > select REMOTEPROC > > > - depends on ARCH_K3 > > > > The original commit seems to indicate there are some platforms > > were this does not build, maybe depend on ARCH_OMAP2PLUS > > Yes, it fails to build on sandbox. If REMOTEPROC_TI_IPU only supports > OMAP SoCs and not K3 SoCs then the prompt text, and perhaps help text > (not in this patch context so I can't see) need to be fixed. The driver > isn't enabled anywhere today, so I don't know that it even compiles, > actually. So it should probably get enabled somewhere, too.
Ah, I see 3/4 and 4/4 enable this on am57xx_evm, OK, good. The rest of what I said applies still however. -- Tom
signature.asc
Description: PGP signature
