From: "Li Yang" <leoli@freescale.com>
To: "Timur Tabi" <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, dan.j.williams@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fsl-dma: allow Freescale Elo DMA driver to be compiled as a module
Date: Thu, 25 Sep 2008 14:54:54 +0800 [thread overview]
Message-ID: <2a27d3730809242354u4cc24b96yda3973bfc3ddac92@mail.gmail.com> (raw)
In-Reply-To: <1222293567-17694-1-git-send-email-timur@freescale.com>
On Thu, Sep 25, 2008 at 5:59 AM, Timur Tabi <timur@freescale.com> wrote:
> Modify the Freescale Elo / Elo Plus DMA driver so that it can be compiled as
> a module.
>
> The primary change is to stop treating the DMA controller as a bus, and the
> DMA channels as devices on the bus. This is because the Open Firmware (OF)
> kernel code does not allow busses to be removed, so although we can call
> of_platform_bus_probe() to probe the DMA channels, there is no
> of_platform_bus_remove(). Instead, the DMA channels are manually probed,
> similar to what fsl_elbc_nand.c does.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
>
> v2: updated per comments
>
> This patch is for the 2.6.28 kernel. This patch exposes a bug in the dmatest
> module, so my other patch "dmatest: properly handle duplicate DMA channels"
> should be applied if this patch is applied.
[snip]
> +static void __exit of_fsl_dma_exit(void)
> +{
> + of_unregister_platform_driver(&of_fsl_dma_driver);
> }
>
> -subsys_initcall(of_fsl_dma_chan_init);
> subsys_initcall(of_fsl_dma_init);
Not a critical problem. But module_init() are preferred for modules.
> +module_exit(of_fsl_dma_exit);
> +
> +MODULE_DESCRIPTION("Freescale Elo / Elo Plus DMA driver");
> +MODULE_LICENSE("GPL");
Acked-by: Li Yang <leoli@freescale.com>
- Leo
next prev parent reply other threads:[~2008-09-25 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 21:59 [PATCH v2] fsl-dma: allow Freescale Elo DMA driver to be compiled as a module Timur Tabi
2008-09-25 6:54 ` Li Yang [this message]
2008-09-25 13:54 ` Timur Tabi
2008-09-25 18:40 ` Scott Wood
2008-09-25 18:47 ` Timur Tabi
2008-09-25 19:00 ` Scott Wood
2008-09-25 19:09 ` Timur Tabi
2008-09-25 20:16 ` Scott Wood
2008-09-27 18:13 ` Dan Williams
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=2a27d3730809242354u4cc24b96yda3973bfc3ddac92@mail.gmail.com \
--to=leoli@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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).