From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.7-rc3
Date: Tue, 30 Oct 2012 10:58:59 -0700 [thread overview]
Message-ID: <20121030175856.GK11908@atomide.com> (raw)
In-Reply-To: <20121030172707.GB3993@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti•com> [121030 10:34]:
> Hi,
>
> On Tue, Oct 30, 2012 at 09:27:28AM -0700, Tony Lindgren wrote:
> > * Vaibhav Hiremath <hvaibhav@ti•com> [121030 07:50]:
> > > >
> > > > MMC is dependent on EDMA-DMA conversion patches from Matt, which he has
> > > > already submitted to the list recently. So MMC support will come along with
> > > > EDMA support. DMA-EDMA patches are targeted for v3.8, lets see how it goes.
> >
> > This is a bogus dependency, the MMC driver needs to also work
> > without DMA.
>
> heh, too bad driver errors out when it doesn't find DMA channels :-)
It should just print a warning instead and continue.
> 1869 host->rx_chan = dma_request_channel(mask, omap_dma_filter_fn, &rx_req);
> 1870 if (!host->rx_chan) {
> 1871 dev_err(mmc_dev(host->mmc), "unable to obtain RX DMA engine channel %u\n", rx_req);
> 1872 ret = -ENXIO;
> 1873 goto err_irq;
> 1874 }
> 1875
> 1876 host->tx_chan = dma_request_channel(mask, omap_dma_filter_fn, &tx_req);
> 1877 if (!host->tx_chan) {
> 1878 dev_err(mmc_dev(host->mmc), "unable to obtain TX DMA engine channel %u\n", tx_req);
> 1879 ret = -ENXIO;
> 1880 goto err_irq;
> 1881 }
>
> in fact, if DMAENGINE isn't enabled, this won't even compile due to
> omap_dma_filter_fn() right ?
It should, CONFIG_DMADEVICES is optional. If it does not compile,
then there's a bug somewhere.
Regards,
Tony
next prev parent reply other threads:[~2012-10-30 17:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 2:36 OMAP baseline test results for v3.7-rc3 Paul Walmsley
2012-10-30 4:39 ` Vaibhav Hiremath
2012-10-30 13:03 ` Paul Walmsley
2012-11-05 2:41 ` Paul Walmsley
2012-11-06 6:09 ` Hiremath, Vaibhav
2012-11-06 10:24 ` Hiremath, Vaibhav
2012-10-30 10:55 ` Mark Jackson
2012-10-30 11:47 ` Paul Walmsley
2012-10-30 12:39 ` Hiremath, Vaibhav
2012-10-30 14:48 ` Vaibhav Hiremath
2012-10-30 16:27 ` Tony Lindgren
2012-10-30 17:27 ` Felipe Balbi
2012-10-30 17:58 ` Tony Lindgren [this message]
2012-10-30 18:51 ` Felipe Balbi
2012-11-06 6:17 ` Hiremath, Vaibhav
2012-11-06 7:58 ` Felipe Balbi
2012-11-06 8:07 ` Hiremath, Vaibhav
2012-11-06 8:05 ` Felipe Balbi
2012-10-31 13:41 ` Mark Jackson
2012-10-31 13:57 ` Hiremath, Vaibhav
2012-10-31 14:24 ` Mark Jackson
2012-11-01 15:52 ` Mark Jackson
2012-11-05 16:54 ` Mark Jackson
2012-11-06 6:16 ` Hiremath, Vaibhav
2012-11-06 9:47 ` Mark Jackson
2012-11-13 15:26 ` Mark Jackson
2012-11-13 15:35 ` Paul Walmsley
2012-11-13 15:57 ` Mark Jackson
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=20121030175856.GK11908@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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