From mboxrd@z Thu Jan 1 00:00:00 1970 From: balbi@ti.com (Felipe Balbi) Date: Tue, 18 Jan 2011 05:10:39 +0200 Subject: [PATCH] omap2-beagle: Depend upon CONFIG_GPIO_TWL4030 In-Reply-To: <1295299548-22839-1-git-send-email-bgamari.foss@gmail.com> References: <1295299548-22839-1-git-send-email-bgamari.foss@gmail.com> Message-ID: <20110118031038.GA2436@legolas.emea.dhcp.ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, On Mon, Jan 17, 2011 at 04:25:48PM -0500, Ben Gamari wrote: > Some very basic setup (i.e. MMC) is done in the beagleboard's setup > callback for the TWL4030's gpio driver, causing a kernel without this > support to fail to find its root filesystem. I can't imagine why one would > want to build a kernel for this board without this driver, so I think > it's worthwhile to explicitly depend on it. > > Signed-Off-By: Ben Gamari > --- > arch/arm/mach-omap2/Kconfig | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig > index ab784bf..74173f1 100644 > --- a/arch/arm/mach-omap2/Kconfig > +++ b/arch/arm/mach-omap2/Kconfig > @@ -120,6 +120,7 @@ config MACH_OMAP_2430SDP > config MACH_OMAP3_BEAGLE > bool "OMAP3 BEAGLE board" > depends on ARCH_OMAP3 > + depends on GPIO_TWL4030 > default y > select OMAP_PACKAGE_CBB NAK. This is totally bogus. The board doesn't really depend on GPIO_TWL4030, the MMC driver does. -- balbi