On Thu, May 21, 2015 at 01:57:07PM +0200, Geert Uytterhoeven wrote:
> Also remove spaces before TABs while we're at it.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
Looks good to me, but the question si which tree does this go thru..
--
~Vinod
> ---
> Documentation/DMA-API-HOWTO.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/DMA-API-HOWTO.txt b/Documentation/DMA-API-HOWTO.txt
> index 0f7afb2bb442e07f..16b6f9509cb65b62 100644
> --- a/Documentation/DMA-API-HOWTO.txt
> +++ b/Documentation/DMA-API-HOWTO.txt
> @@ -240,7 +240,7 @@ the case would look like this:
>
> if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(64))) {
> using_dac = 1;
> - consistent_using_dac = 1;
> + consistent_using_dac = 1;
> } else if (!dma_set_mask_and_coherent(dev, DMA_BIT_MASK(32))) {
> using_dac = 0;
> consistent_using_dac = 0;
> @@ -353,7 +353,7 @@ There are two types of DMA mappings:
> transfer, unmapped right after it (unless you use dma_sync_* below)
> and for which hardware can optimize for sequential accesses.
>
> - This of "streaming" as "asynchronous" or "outside the coherency
> + Think of "streaming" as "asynchronous" or "outside the coherency
> domain".
>
> Good examples of what to use streaming mappings for are:
> --
> 1.9.1
>
--
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
