From: "Dan Williams" <dan.j.williams@intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Adrian Bunk <bunk@kernel.org>,
Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
Pierre Ossman <drzeus-list@drzeus.cx>,
linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
kernel@avr32linux.org, "Nelson,
Shannon" <shannon.nelson@intel.com>
Subject: Re: [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for AVR32 users
Date: Fri, 27 Jun 2008 11:31:49 -0700 [thread overview]
Message-ID: <e9c3a7c20806271131i5a4f5afg94fd21a89923ffbb@mail.gmail.com> (raw)
In-Reply-To: <200806271124.42783.david-b@pacbell.net>
On Fri, Jun 27, 2008 at 11:24 AM, David Brownell <david-b@pacbell.net> wrote:
> On Friday 27 June 2008, Adrian Bunk wrote:
>> The only effect of the HAVE_DMA_ENGINE would be to not show an empty
>> kconfig menu.
>
> Well, no. It would also make the network layer memcpy "acceleration"
> option unavailable when there was no underlying engine ... similarly
> with other pointless "we don't have that subsystem here" options.
>
Take another look. NET_DMA depends on DMA_ENGINE which only gets
selected when a dma device driver is selected. Each driver has its
architecture specific dependency, so the DMADEVICES arch dependency
was completely redundant.
> Plus it would help ensure that the arch dependencies are comprehenible,
> unlike that highmem thing.
The highmem dependency can go away its only purpose is to prevent
hitting the BUILD_BUG_ON in async_xor.c.
--
Dan
next prev parent reply other threads:[~2008-06-27 18:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 13:23 [PATCH v4 0/6] dmaengine/mmc: DMA slave interface and two new drivers Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 1/6] dmaengine: Add dma_client parameter to device_alloc_chan_resources Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 2/6] dmaengine: Add dma_chan_is_in_use() function Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 3/6] dmaengine: Add slave DMA interface Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for AVR32 users Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 5/6] dmaengine: Driver for the Synopsys DesignWare DMA controller Haavard Skinnemoen
2008-06-26 13:23 ` [PATCH v4 6/6] Atmel MCI: Driver for Atmel on-chip MMC controllers Haavard Skinnemoen
2008-06-27 19:10 ` Haavard Skinnemoen
2008-06-27 19:56 ` Pierre Ossman
2008-06-28 12:43 ` Haavard Skinnemoen
2008-06-28 13:31 ` Haavard Skinnemoen
2008-06-29 16:49 ` Pierre Ossman
2008-06-28 13:45 ` Pierre Ossman
2008-06-28 14:01 ` Haavard Skinnemoen
2008-06-28 14:11 ` Pierre Ossman
2008-06-27 21:31 ` Dan Williams
2008-06-28 12:47 ` Haavard Skinnemoen
2008-07-04 0:40 ` dmaengine skip unmap (was: Re: [PATCH v4 5/6] dmaengine: Driver for the Synopsys DesignWare DMA controller) Dan Williams
2008-07-04 14:47 ` Haavard Skinnemoen
2008-06-26 14:15 ` [PATCH v4 4/6] dmaengine: Make DMA Engine menu visible for AVR32 users Adrian Bunk
2008-06-26 14:46 ` Haavard Skinnemoen
2008-06-27 0:59 ` Dan Williams
2008-06-27 16:37 ` David Brownell
2008-06-27 17:44 ` Adrian Bunk
2008-06-27 18:24 ` David Brownell
2008-06-27 18:29 ` Adrian Bunk
2008-06-27 18:31 ` Dan Williams [this message]
2008-06-27 18:13 ` Haavard Skinnemoen
2008-06-26 20:04 ` David Brownell
2008-06-26 13:32 ` [PATCH v4 3/6] dmaengine: Add slave DMA interface Haavard Skinnemoen
2008-06-28 12:29 ` Haavard Skinnemoen
2008-07-02 1:31 ` [PATCH v4 2/6] dmaengine: Add dma_chan_is_in_use() function Dan Williams
2008-07-02 2:00 ` Dan Williams
2008-07-02 7:59 ` Haavard Skinnemoen
2008-07-02 7:56 ` Haavard Skinnemoen
2008-07-04 1:06 ` [PATCH v4 0/6] dmaengine/mmc: DMA slave interface and two new drivers Dan Williams
2008-07-04 15:13 ` Haavard Skinnemoen
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=e9c3a7c20806271131i5a4f5afg94fd21a89923ffbb@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=bunk@kernel.org \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shannon.nelson@intel.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).