From: "Timur Tabi" <timur@freescale.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, dan.j.williams@intel.com,
Li Yang <leoli@freescale.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 13:47:52 -0500 [thread overview]
Message-ID: <ed82fe3e0809251147t30743080v593d194eba731a7b@mail.gmail.com> (raw)
In-Reply-To: <20080925184020.GA5230@ld0162-tx32.am.freescale.net>
On Thu, Sep 25, 2008 at 1:40 PM, Scott Wood <scottwood@freescale.com> wrote:
> If there's a dependency there, how will it work when this is built as a
> module?
There are no dependencies. fsldma registers with the DMA engine,
which is always built in-kernel. The DMA engine is what handles
linking DMA clients to DMA drivers. The DMA clients get a callback
whenever a DMA driver registers with the DMA engine. If the DMA
driver is already registered when the client registers, then the
client will get a callback immediately after it registers.
I chose subsys_initcall() to increase the probability that fsldma is
already present when DMA clients are loaded/initialized and register.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-25 18:47 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
2008-09-25 13:54 ` Timur Tabi
2008-09-25 18:40 ` Scott Wood
2008-09-25 18:47 ` Timur Tabi [this message]
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=ed82fe3e0809251147t30743080v593d194eba731a7b@mail.gmail.com \
--to=timur@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@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).