public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Dragos Tatulea <dtatulea@ixiacom.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Octavian Purdila <opurdila@ixiacom.com>
Subject: Re: DMA_ENGINE: can't use it without selecting a dma engine driver
Date: Wed, 17 Jun 2009 09:38:30 -0700	[thread overview]
Message-ID: <4A391C06.2060302@intel.com> (raw)
In-Reply-To: <20090617181204.52981f5f@dragos-tp.localdomain>

Dragos Tatulea wrote:
> Hi,
> 
>>>        Just discovered that it's impossible to select the dma engine
>>> without compiling a dma engine driver from the kernel. What if I want to
>>> use a different dma engine?
>>>
>> Create a Kconfig entry for your driver in drivers/dma/Kconfig and have
>> it "select DMA_ENGINE".
> That's what I want to avoid. The dma engine driver is out of tree.
> 
> What is the rationale behind this? It seems (to me) impossible to have all
> such drivers in upstream.

It is very straightforward to have all drivers upstream, just send the 
code [1].

The rationale for this configuration scheme is to turn off a lot of 
unnecessary code when we know at build time that a dma driver will never 
be loaded.

If you must keep your driver out of tree simply maintain another out of 
tree patch that allows DMA_ENGINE to be manually enabled.

Regards,
Dan

[1]: http://www.kernel.org/doc/Documentation/SubmittingDrivers


      reply	other threads:[~2009-06-17 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 21:53 DMA_ENGINE: can't use it without selecting a dma engine driver Dragos Tatulea
2009-06-17  6:40 ` Dan Williams
2009-06-17 15:12   ` Dragos Tatulea
2009-06-17 16:38     ` Dan Williams [this message]

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=4A391C06.2060302@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=dtatulea@ixiacom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opurdila@ixiacom.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