1. Depend on OMAP_IOMMU instead of selecting it, to fix an unmet direct dependency of it (and its imminent build error) 2. Set default to 'no' (achieved implicitly by dropping the 'default' line)
Reported-by: Russell King <[email protected]> Signed-off-by: Ohad Ben-Cohen <[email protected]> Cc: Grant Likely <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Mark Grosen <[email protected]> Cc: Suman Anna <[email protected]> Cc: Fernando Guzman Lugo <[email protected]> Cc: Rob Clark <[email protected]> Cc: Ludovic BARRE <[email protected]> Cc: Loic PALLARDY <[email protected]> Cc: Omar Ramirez Luna <[email protected]> Cc: Russell King <[email protected]> --- drivers/remoteproc/Kconfig | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig index 25fc4cc..24d880e 100644 --- a/drivers/remoteproc/Kconfig +++ b/drivers/remoteproc/Kconfig @@ -8,11 +8,10 @@ config REMOTEPROC config OMAP_REMOTEPROC tristate "OMAP remoteproc support" depends on ARCH_OMAP4 - select OMAP_IOMMU + depends on OMAP_IOMMU select REMOTEPROC select OMAP_MBOX_FWK select RPMSG - default m help Say y here to support OMAP's remote processors (dual M3 and DSP on OMAP4) via the remote processor framework. -- 1.7.5.4 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
