linux-kernel - Re: [PATCH] fix starting of transfers in i.MX dma drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Jan 2012 14:42:44 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	Sascha Hauer <s.hauer@...gutronix.de>
Cc:	linux-arm-kernel@...ts.infradead.org, Chris Ball <cjb@...top.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Javier Martin <javier.martin@...ta-silicon.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fix starting of transfers in i.MX dma drivers

On Mon, 2012-01-09 at 10:32 +0100, Sascha Hauer wrote:
> This moves the start of transfers from tx_submit to issue_pending
> for the i.MX dma drivers as requested by Vinoud here:
> 
> https://lkml.org/lkml/2012/1/7/23
> 
> This requires the users (mxcmmc and i.MX sound) to be fixed first.
> So Chris, Mark, given your Ack I would suggest to send this via
> Vinouds DMA tree.
> 
> Sascha
> 
> Sascha Hauer (4):
>       mmc: mxcmmc: add missing dma_async_issue_pending
>       ASoC: i.MX: Add missing dma_async_issue_pending
>       dma: imx-dma: start transfer in issue_pending
>       dma: imx-sdma: start transfer in issue_pending
> 
>  drivers/dma/imx-dma.c           |    9 ++++-----
>  drivers/dma/imx-sdma.c          |   11 +++++------
>  drivers/mmc/host/mxcmmc.c       |    1 +
>  sound/soc/imx/imx-pcm-dma-mx2.c |    1 +
>  4 files changed, 11 insertions(+), 11 deletions(-)

Thanks applied all.

Fixed change log in 3 & 4, as Russell pointed out

Got a conflict in 4, pls see that fix is right.

-- 
~Vinod

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/