From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com> To: "S, Venkatraman" <svenkatr@ti.com> Cc: Javier Martinez Canillas <martinez.javier@gmail.com>, Tony Lindgren <tony@atomide.com>, Javier Martinez Canillas <javier@dowhile0.org>, Kevin Hilman <khilman@ti.com>, Russell King <linux@arm.linux.org.uk>, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Chris Ball <cjb@laptop.org>, linux-mmc@vger.kernel.org Subject: Re: [PATCH 1/1] mmc: host: enable OMAP DMA engine support for omap hosts by default Date: Wed, 18 Jul 2012 15:14:28 +0530 [thread overview] Message-ID: <CAMQu2gy+uXJFfmOwLX=YH41pr-N+T28-1wLo5rXEaj9MGffHPw@mail.gmail.com> (raw) In-Reply-To: <CANfBPZ_N4ZK5PgFQLHWMwsG60tb-FPTjeieTJ92rBUNgONAxAw@mail.gmail.com> On Wed, Jul 18, 2012 at 3:08 PM, S, Venkatraman <svenkatr@ti.com> wrote: > On Wed, Jul 18, 2012 at 2:46 PM, Javier Martinez Canillas > <martinez.javier@gmail.com> wrote: [...] >>>> >>>> And what about enabling it at the SoC config level but making the >>>> drivers dependant on CONFIG_DMADEVICES and CONFIG_DMA_OMAP? If you >>>> agree I can send something like this in two different patches (one for >>>> the omap2plus_defconfig and another to make the drivers dependant on >>>> the config option): >>>> >>>> diff --git a/arch/arm/configs/omap2plus_defconfig >>>> b/arch/arm/configs/omap2plus_defconfig >>>> index b152de7..e58edc3 100644 >>>> --- a/arch/arm/configs/omap2plus_defconfig >>>> +++ b/arch/arm/configs/omap2plus_defconfig >>>> @@ -193,6 +193,8 @@ CONFIG_MMC_OMAP_HS=y >>>> CONFIG_RTC_CLASS=y >>>> CONFIG_RTC_DRV_TWL92330=y >>>> CONFIG_RTC_DRV_TWL4030=y >>>> +CONFIG_DMADEVICES=y >>>> +CONFIG_DMA_OMAP=y >>>> CONFIG_EXT2_FS=y >>>> CONFIG_EXT3_FS=y >>>> # CONFIG_EXT3_FS_XATTR is not set >>>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig >>>> index aa131b3..314c7bd 100644 >>>> --- a/drivers/mmc/host/Kconfig >>>> +++ b/drivers/mmc/host/Kconfig >>>> @@ -231,7 +231,7 @@ config MMC_SDHCI_S3C_DMA >>>> >>>> config MMC_OMAP >>>> tristate "TI OMAP Multimedia Card Interface support" >>>> - depends on ARCH_OMAP >>>> + depends on ARCH_OMAP && DMADEVICES && DMA_OMAP >>> >>> May be. But since for sure a driver knows that it needs DMA >>> support to be enabled, I will just select it rather than depends >>> on. >>> >>> Regards >>> santosh >> >> Yes I agree with you, I was just exploring other options :-) >> > For MMC atleast, there's already a patch in mmc-next to do a "Depends On" > http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=7c68046c99f0b96d965c31cf42814b9a0f15ad46 Change log assumes says . "The patch simply make them depend on DMA_OMAP since DMA_OMAP will select DMA_ENGINE automatically" This won't be true if the DMA selection are not done at ARCH_OMAP level as discussed in this thread. Having said that, I think Russell and Tony need to take call on how this needs to be handled. Regards Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Shilimkar, Santosh) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 1/1] mmc: host: enable OMAP DMA engine support for omap hosts by default Date: Wed, 18 Jul 2012 15:14:28 +0530 [thread overview] Message-ID: <CAMQu2gy+uXJFfmOwLX=YH41pr-N+T28-1wLo5rXEaj9MGffHPw@mail.gmail.com> (raw) In-Reply-To: <CANfBPZ_N4ZK5PgFQLHWMwsG60tb-FPTjeieTJ92rBUNgONAxAw@mail.gmail.com> On Wed, Jul 18, 2012 at 3:08 PM, S, Venkatraman <svenkatr@ti.com> wrote: > On Wed, Jul 18, 2012 at 2:46 PM, Javier Martinez Canillas > <martinez.javier@gmail.com> wrote: [...] >>>> >>>> And what about enabling it at the SoC config level but making the >>>> drivers dependant on CONFIG_DMADEVICES and CONFIG_DMA_OMAP? If you >>>> agree I can send something like this in two different patches (one for >>>> the omap2plus_defconfig and another to make the drivers dependant on >>>> the config option): >>>> >>>> diff --git a/arch/arm/configs/omap2plus_defconfig >>>> b/arch/arm/configs/omap2plus_defconfig >>>> index b152de7..e58edc3 100644 >>>> --- a/arch/arm/configs/omap2plus_defconfig >>>> +++ b/arch/arm/configs/omap2plus_defconfig >>>> @@ -193,6 +193,8 @@ CONFIG_MMC_OMAP_HS=y >>>> CONFIG_RTC_CLASS=y >>>> CONFIG_RTC_DRV_TWL92330=y >>>> CONFIG_RTC_DRV_TWL4030=y >>>> +CONFIG_DMADEVICES=y >>>> +CONFIG_DMA_OMAP=y >>>> CONFIG_EXT2_FS=y >>>> CONFIG_EXT3_FS=y >>>> # CONFIG_EXT3_FS_XATTR is not set >>>> diff --git a/drivers/mmc/host/Kconfig b/drivers/mmc/host/Kconfig >>>> index aa131b3..314c7bd 100644 >>>> --- a/drivers/mmc/host/Kconfig >>>> +++ b/drivers/mmc/host/Kconfig >>>> @@ -231,7 +231,7 @@ config MMC_SDHCI_S3C_DMA >>>> >>>> config MMC_OMAP >>>> tristate "TI OMAP Multimedia Card Interface support" >>>> - depends on ARCH_OMAP >>>> + depends on ARCH_OMAP && DMADEVICES && DMA_OMAP >>> >>> May be. But since for sure a driver knows that it needs DMA >>> support to be enabled, I will just select it rather than depends >>> on. >>> >>> Regards >>> santosh >> >> Yes I agree with you, I was just exploring other options :-) >> > For MMC atleast, there's already a patch in mmc-next to do a "Depends On" > http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=7c68046c99f0b96d965c31cf42814b9a0f15ad46 Change log assumes says . "The patch simply make them depend on DMA_OMAP since DMA_OMAP will select DMA_ENGINE automatically" This won't be true if the DMA selection are not done at ARCH_OMAP level as discussed in this thread. Having said that, I think Russell and Tony need to take call on how this needs to be handled. Regards Santosh
next prev parent reply other threads:[~2012-07-18 9:44 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <1342485005-5178-1-git-send-email-javier@dowhile0.org> 2012-07-17 6:45 ` [PATCH 1/1] mmc: host: enable OMAP DMA engine support for omap hosts by default Shilimkar, Santosh 2012-07-17 6:45 ` Shilimkar, Santosh 2012-07-17 6:51 ` Javier Martinez Canillas 2012-07-17 6:51 ` Javier Martinez Canillas 2012-07-18 6:59 ` Tony Lindgren 2012-07-18 6:59 ` Tony Lindgren 2012-07-18 7:04 ` Shilimkar, Santosh 2012-07-18 7:04 ` Shilimkar, Santosh 2012-07-18 7:10 ` Tony Lindgren 2012-07-18 7:10 ` Tony Lindgren 2012-07-18 7:44 ` S, Venkatraman 2012-07-18 7:44 ` S, Venkatraman 2012-07-18 8:36 ` Shilimkar, Santosh 2012-07-18 8:36 ` Shilimkar, Santosh 2012-07-18 8:49 ` Javier Martinez Canillas 2012-07-18 8:49 ` Javier Martinez Canillas 2012-07-18 9:11 ` Shilimkar, Santosh 2012-07-18 9:11 ` Shilimkar, Santosh 2012-07-18 9:16 ` Javier Martinez Canillas 2012-07-18 9:16 ` Javier Martinez Canillas 2012-07-18 9:38 ` S, Venkatraman 2012-07-18 9:38 ` S, Venkatraman 2012-07-18 9:44 ` Shilimkar, Santosh [this message] 2012-07-18 9:44 ` Shilimkar, Santosh 2012-07-19 11:32 ` Tony Lindgren 2012-07-19 11:32 ` Tony Lindgren 2012-07-20 9:28 ` S, Venkatraman 2012-07-20 9:28 ` S, Venkatraman 2012-07-20 10:01 ` S, Venkatraman 2012-07-20 10:01 ` S, Venkatraman 2012-08-23 21:00 ` Peter Meerwald 2012-08-23 21:00 ` Peter Meerwald 2012-08-24 7:10 ` Shilimkar, Santosh 2012-08-24 7:10 ` Shilimkar, Santosh 2012-08-24 7:51 ` Peter Meerwald 2012-08-24 7:51 ` Peter Meerwald 2012-08-24 9:42 ` Russell King - ARM Linux 2012-08-24 9:42 ` Russell King - ARM Linux 2012-08-24 10:21 ` Shilimkar, Santosh 2012-08-24 10:21 ` Shilimkar, Santosh 2012-08-24 10:39 ` Russell King - ARM Linux 2012-08-24 10:39 ` Russell King - ARM Linux 2012-08-24 10:45 ` Shilimkar, Santosh 2012-08-24 10:45 ` Shilimkar, Santosh 2012-08-24 12:10 ` Peter Meerwald 2012-08-24 12:10 ` Peter Meerwald 2012-08-25 7:57 ` Russell King - ARM Linux 2012-08-25 7:57 ` Russell King - ARM Linux 2012-07-18 8:25 ` Javier Martinez Canillas 2012-07-18 8:25 ` Javier Martinez Canillas 2012-07-19 11:31 ` Tony Lindgren 2012-07-19 11:31 ` Tony Lindgren
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMQu2gy+uXJFfmOwLX=YH41pr-N+T28-1wLo5rXEaj9MGffHPw@mail.gmail.com' \ --to=santosh.shilimkar@ti.com \ --cc=cjb@laptop.org \ --cc=javier@dowhile0.org \ --cc=khilman@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-mmc@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=martinez.javier@gmail.com \ --cc=svenkatr@ti.com \ --cc=tony@atomide.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.