From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH 4/5] ASoC: rcar: Fix dma direction type
Date: Thu, 19 Jun 2014 02:38:44 -0700 (PDT)
Message-ID: <87ppi5nsrc.wl%kuninori.morimoto.gx@renesas.com>
References: <1403163631-26215-1-git-send-email-lars@metafoo.de>
 <1403163631-26215-5-git-send-email-lars@metafoo.de>
 <87wqcdntzh.wl%kuninori.morimoto.gx@renesas.com>
 <53A2AC69.6080508@metafoo.de>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com
 [209.85.192.172])
 by alsa0.perex.cz (Postfix) with ESMTP id B37F32619F3
 for <alsa-devel@alsa-project.org>; Thu, 19 Jun 2014 11:38:46 +0200 (CEST)
Received: by mail-pd0-f172.google.com with SMTP id w10so1662168pde.17
 for <alsa-devel@alsa-project.org>; Thu, 19 Jun 2014 02:38:45 -0700 (PDT)
In-Reply-To: <53A2AC69.6080508@metafoo.de>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Brian Austin <brian.austin@cirrus.com>, alsa-devel@alsa-project.org, Paul Handrigan <Paul.Handrigan@cirrus.com>, Liam Girdwood <lgirdwood@gmail.com>, Peter Ujfalusi <peter.ujfalusi@ti.com>, Mark Brown <broonie@kernel.org>, Jyri Sarha <jsarha@ti.com>, Jarkko Nikula <jarkko.nikula@bitmer.com>
List-Id: alsa-devel@alsa-project.org


Hi Lars

> >> dmaengine_prep_slave_single() expects a enum dma_transfer_direction and not a
> >> enum dma_data_direction. Since the integer representations of both DMA_TO_DEVICE
> >> and DMA_MEM_TO_DEV aswell as DMA_FROM_DEVICE and DMA_DEV_TO_MEM have the same
> >> value the code worked fine even though it was using the wrong type.
> >>
> >> Fixes the following warning from sparse:
> >> 	sound/soc/sh/rcar/core.c:227:49: warning: mixing different enum types
> >> 	sound/soc/sh/rcar/core.c:227:49:     int enum dma_data_direction  versus
> >> 	sound/soc/sh/rcar/core.c:227:49:     int enum dma_transfer_direction
> >>
> >> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> >> ---
> >
> > Acked-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> >
> > Actually, ${LINUX}/sound/soc/sh/fsi.c :: fsi_dma_transfer()
> > is using enum dma_data_direction to dmaengine_prep_dma_cyclic()
> > Does it have same issue ?
> 
> Yes, but the fix for that should go in after your "ASoC: fsi: use 
> SNDRV_DMA_TYPE_DEV for sound buffer" patch, because otherwise the fix just 
> introduces a new warning because before that patch dir is also passed to 
> dma_sync_single_xxx() which wants a enum dma_data_direction.

Ahh, yes, indeed
Thank you for your explain