On Mon, Apr 23, 2012 at 6:05 PM, Russell King
<[email protected]> wrote:

> Add DMA engine support to the OMAP HSMMC driver.  This supplements the
> private DMA API implementation contained within this driver, and the
> driver can be switched at build time between using DMA engine and the
> private DMA API.
>
> Signed-off-by: Russell King <[email protected]>

Great,

> +#if 1
> +               sig = host->dma_line_rx;
> +               host->rx_chan = dma_request_channel(mask, omap_dma_filter_fn, 
> &sig);
> +               if (!host->rx_chan) {
> +                       dev_warn(mmc_dev(host->mmc), "unable to obtain RX DMA 
> engine channel %u\n", sig);
> +               }
> +#endif
> +#if 1
> +               sig = host->dma_line_tx;
> +               host->tx_chan = dma_request_channel(mask, omap_dma_filter_fn, 
> &sig);
> +               if (!host->tx_chan) {
> +                       dev_warn(mmc_dev(host->mmc), "unable to obtain TX DMA 
> engine channel %u\n", sig);
> +               }
> +#endif

Are these development artifacts?

Apart from that:
Acked-by: Linus Walleij <[email protected]>

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to