From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mmc: host: enable OMAP DMA engine support for omap hosts by default
Date: Tue, 17 Jul 2012 23:59:51 -0700 [thread overview]
Message-ID: <20120718065951.GH6522@atomide.com> (raw)
In-Reply-To: <CABxcv=nsmeVLspzXERYXebmPaNO6rKCsVnak7dMtvGjiYH4vOw@mail.gmail.com>
* Javier Martinez Canillas <javier@dowhile0.org> [120716 23:56]:
> On Tue, Jul 17, 2012 at 8:45 AM, Shilimkar, Santosh
> <santosh.shilimkar@ti.com> wrote:
> > Hi,
> >
> > On Tue, Jul 17, 2012 at 6:00 AM, Javier Martinez Canillas
> > <javier@dowhile0.org> wrote:
> >> The OMAP MMC and OMAP High Speed MMC hosts now use entirely the DMA
> >> engine API instead of the previous private DMA API implementation.
> >>
> >> So, if the kernel is built with support for any of these hosts but it
> >> doesn't support DMA devices nor OMAP DMA support, it fails when trying
> >> to obtain a DMA channel which leads to the following error on an OMAP3
> >> IGEPv2 Rev.C board (and probably on most OMAP boards with MMC support):
> >>
> >> [ 2.199981] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48
> >> [ 2.215087] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62
> >>
> >> selecting automatically CONFIG_DMADEVICES and CONFIG_DMA_OMAP solves it.
> >>
> >> Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
> >> ---
> > Considering, we are updating drivers to select the DMA engine, can you
> > also include
> > "drivers/spi/spi-omap2-mcspi.c" which is also updated for DMA engine.
> >
> > Regards
> > Santosh
>
> Hi Santosh,
>
> Ok, I'll send a v2 now which includes spi-omap2-mcspi then.
I don't think we should do this, the drivers should work with and without
dma. This just needs to be added to the omap2plus_defconfig.
Regards,
Tony
next prev parent reply other threads:[~2012-07-18 6:59 UTC|newest]
Thread overview: 26+ 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:51 ` Javier Martinez Canillas
2012-07-18 6:59 ` Tony Lindgren [this message]
2012-07-18 7:04 ` Shilimkar, Santosh
2012-07-18 7:10 ` Tony Lindgren
2012-07-18 7:44 ` S, Venkatraman
2012-07-18 8:36 ` Shilimkar, Santosh
2012-07-18 8:49 ` Javier Martinez Canillas
2012-07-18 9:11 ` Shilimkar, Santosh
2012-07-18 9:16 ` Javier Martinez Canillas
2012-07-18 9:38 ` S, Venkatraman
2012-07-18 9:44 ` Shilimkar, Santosh
2012-07-19 11:32 ` Tony Lindgren
2012-07-20 9:28 ` S, Venkatraman
2012-07-20 10:01 ` S, Venkatraman
2012-08-23 21:00 ` Peter Meerwald
2012-08-24 7:10 ` Shilimkar, Santosh
2012-08-24 7:51 ` Peter Meerwald
2012-08-24 9:42 ` Russell King - ARM Linux
2012-08-24 10:21 ` Shilimkar, Santosh
2012-08-24 10:39 ` Russell King - ARM Linux
2012-08-24 10:45 ` Shilimkar, Santosh
2012-08-24 12:10 ` Peter Meerwald
2012-08-25 7:57 ` Russell King - ARM Linux
2012-07-18 8:25 ` Javier Martinez Canillas
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=20120718065951.GH6522@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).