From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 01/13] dmaengine: imx-dma: merge old dma-v1.c with imx-dma.c
Date: Fri, 9 Mar 2012 12:00:28 +0100 [thread overview]
Message-ID: <20120309110028.GB3852@pengutronix.de> (raw)
In-Reply-To: <1331130825-14947-2-git-send-email-javier.martin@vista-silicon.com>
On Wed, Mar 07, 2012 at 03:33:33PM +0100, Javier Martin wrote:
> It is mainly a simple merge changing the prefix of some
> functions to fit the imx-dma namings.
>
> As there are no users of the old dma-v1.c api we can safely
> remove this file.
>
> Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
> ---
> @@ -633,11 +1127,8 @@ static int __exit imxdma_remove(struct platform_device *pdev)
>
> dma_async_device_unregister(&imxdma->dma_device);
>
> - for (i = 0; i < MAX_DMA_CHANNELS; i++) {
> - struct imxdma_channel *imxdmac = &imxdma->channel[i];
> -
> - imx_dma_free(imxdmac->imxdma_channel);
> - }
> + for (i = 0; i < MAX_DMA_CHANNELS; i++)
> + free_irq(MX2x_INT_DMACH0 + i, NULL);
This lacks a test for i.MX1/21/27. The above is correct for i.MX21/27,
but on i.MX1 you have to free MX1_DMA_INT/MX1_DMA_ERR.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-03-09 11:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 14:33 [PATCH v2 00/13] dmaengine: imx-dma: merge dma arch code into dmaengine Javier Martin
2012-03-07 14:33 ` [PATCH v2 01/13] dmaengine: imx-dma: merge old dma-v1.c with imx-dma.c Javier Martin
2012-03-09 11:00 ` Sascha Hauer [this message]
2012-03-09 11:57 ` javier Martin
2012-03-07 14:33 ` [PATCH v2 02/13] dmaengine: imx-dma: remove data member from internal structure Javier Martin
2012-03-07 14:33 ` [PATCH v2 03/13] dmaengine: imx-dma: remove dma_mode member of " Javier Martin
2012-03-07 14:33 ` [PATCH v2 04/13] dmaengine: imx-dma: remove 'imxdma_setup_mem2mem_hw' function Javier Martin
2012-03-07 14:33 ` [PATCH v2 05/13] dmaengine: imx-dma: remove 'imxdma_config_channel_hw' function Javier Martin
2012-03-07 14:33 ` [PATCH v2 06/13] dmaengine: imx-dma: remove 'imxdma_setup_sg_hw' function Javier Martin
2012-03-07 14:33 ` [PATCH v2 07/13] dmaengine: imx-dma: remove sg member from internal structure Javier Martin
2012-03-07 14:33 ` [PATCH v2 08/13] dmaengine: imx-dma: remove 'in_use' field of 'internal' structure Javier Martin
2012-03-07 14:33 ` [PATCH v2 09/13] dmaengine: imx-dma: remove 'resbytes' " Javier Martin
2012-03-07 14:33 ` [PATCH v2 10/13] dmaengine: imx-dma: remove internal structure Javier Martin
2012-03-07 14:33 ` [PATCH v2 11/13] dmaengine: imx-dma: remove unused arg of imxdma_sg_next Javier Martin
2012-03-07 14:33 ` [PATCH v2 12/13] dmaengine: imx-dma: remove 'imx_dmav1_baseaddr' and 'dma_clk' Javier Martin
2012-03-07 14:33 ` [PATCH v2 13/13] dmaengine: imx-dma: use 'dev_dbg' and 'dev_warn' for messages Javier Martin
2012-03-08 20:04 ` [PATCH v2 00/13] dmaengine: imx-dma: merge dma arch code into dmaengine Sascha Hauer
2012-03-09 8:00 ` javier Martin
2012-03-09 10:56 ` Sascha Hauer
2012-03-09 12:04 ` javier Martin
2012-03-09 13:08 ` Sascha Hauer
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=20120309110028.GB3852@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).