From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Date: Wed, 23 Jun 2010 06:47:43 +0000 Subject: Re: [PATCH] initialise DMA engine before MMC Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Guennadi Liakhovetski Cc: linux-kernel@vger.kernel.org, "linux-sh@vger.kernel.org" , Dan Williams , Greg Kroah-Hartman , linux-mmc@vger.kernel.org 2010/6/7 Guennadi Liakhovetski : > To use DMA engine based DMA with MMC in a non-modular build, the DMA > engine has to initialise before MMC. > > Signed-off-by: Guennadi Liakhovetski > --- > diff --git a/drivers/Makefile b/drivers/Makefile > index 91874e0..b713e75 100644 > --- a/drivers/Makefile > +++ b/drivers/Makefile > @@ -92,6 +92,7 @@ obj-$(CONFIG_EISA) =A0 =A0 =A0 =A0 =A0 =A0+=3D eisa/ > =A0obj-y =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+=3D lguest/ > =A0obj-$(CONFIG_CPU_FREQ) =A0 =A0 =A0 =A0 +=3D cpufreq/ > =A0obj-$(CONFIG_CPU_IDLE) =A0 =A0 =A0 =A0 +=3D cpuidle/ > +obj-$(CONFIG_DMA_ENGINE) =A0 =A0 =A0 +=3D dma/ > =A0obj-$(CONFIG_MMC) =A0 =A0 =A0 =A0 =A0 =A0 =A0+=3D mmc/ > =A0obj-$(CONFIG_MEMSTICK) =A0 =A0 =A0 =A0 +=3D memstick/ > =A0obj-$(CONFIG_NEW_LEDS) =A0 =A0 =A0 =A0 +=3D leds/ > @@ -102,7 +103,6 @@ obj-$(CONFIG_CRYPTO) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0+= =3D crypto/ > =A0obj-$(CONFIG_SUPERH) =A0 =A0 =A0 =A0 =A0 +=3D sh/ > =A0obj-$(CONFIG_ARCH_SHMOBILE) =A0 =A0+=3D sh/ > =A0obj-$(CONFIG_GENERIC_TIME) =A0 =A0 +=3D clocksource/ > -obj-$(CONFIG_DMA_ENGINE) =A0 =A0 =A0 +=3D dma/ > =A0obj-$(CONFIG_DCA) =A0 =A0 =A0 =A0 =A0 =A0 =A0+=3D dca/ > =A0obj-$(CONFIG_HID) =A0 =A0 =A0 =A0 =A0 =A0 =A0+=3D hid/ > =A0obj-$(CONFIG_PPC_PS3) =A0 =A0 =A0 =A0 =A0+=3D ps3/ What I did was to move my DMA engines to subsystem_initcall(), with this approach I would have had to rearrange a lot of subsystems I think. But if it's easier for you this way by all means do it. Yours, Linus Walleij