From: Jeff Garzik <jgarzik@pobox.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Robert Hancock <hancockrwd@gmail.com>,
Tejun Heo <htejun@gmail.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
alan@lxorguk.ukuu.org.uk, flar@allandria.com,
schmitz@biophys.uni-duesseldorf.de, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, takata@linux-m32r.org,
geert@linux-m68k.org, linux-m68k@vger.kernel.org,
ysato@users.sourceforge.jp
Subject: Re: [PATCH] asm-generic: add a dma-mapping.h file
Date: Mon, 18 May 2009 18:54:49 -0400 [thread overview]
Message-ID: <4A11E739.6080106@pobox.com> (raw)
In-Reply-To: <200905172245.23774.arnd@arndb.de>
Arnd Bergmann wrote:
> h8300 and m32r currently do not provide a DMA mapping API
> and therefore cannot use the ATA drivers. This adds a
> generic version of dma-mapping.h for architectures that
> have none or very minimal actual support for DMA in hardware
> and makes the two architectures use it.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> On Sunday 17 May 2009 20:05:54 Jeff Garzik wrote:
>
>> That's what needs to happen. We provide no-op functions for e.g. PCI
>> and x86 DMI, for platforms where this support does not exist.
>>
>> Pretty much all architectures support some form of ATA. m68k, m32r,
>> h8300 and microblaze all have IDE interface, which means that libata
>> needs to work on that platform.
>>
>> The only !ATA arch in the entire kernel is s390, AFAICT.
>
> m68k only defines NO_DMA for Sun3 and Dragonball. Sun3 does
> not have ATA, Dragonball could probably just enable HAS_DMA.
>
> ---
> arch/h8300/Kconfig | 2 +-
> arch/h8300/include/asm/dma-mapping.h | 1 +
> arch/m32r/Kconfig | 2 +-
> arch/m32r/include/asm/dma-mapping.h | 1 +
> include/asm-generic/dma-mapping.h | 399 ++++++++++++++++++++++++++++++++++
> 5 files changed, 403 insertions(+), 2 deletions(-)
> create mode 100644 arch/h8300/include/asm/dma-mapping.h
> create mode 100644 arch/m32r/include/asm/dma-mapping.h
> create mode 100644 include/asm-generic/dma-mapping.h
My main comment is a bit non-specific... I tend to think that all
no-dma platforms should provide an API whose implementation always
returns errors, e.g. an inlined version of dma-mapping-broken.h.
That sort of setup permits the compiler's dead code elimination to work
on these no-dma platforms, while not crapping up the libata code with a
bunch of ifdefs.
Jeff
next prev parent reply other threads:[~2009-05-18 22:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090511222702.352192505@arndb.de>
2009-05-11 22:38 ` [PATCH] ata: libata depends on HAS_DMA Arnd Bergmann
2009-05-12 0:58 ` Jeff Garzik
2009-05-12 12:40 ` Arnd Bergmann
2009-05-12 13:05 ` Arnd Bergmann
2009-05-12 8:06 ` Alan Cox
2009-05-12 9:23 ` Arnd Bergmann
2009-05-13 3:30 ` Brad Boyer
2009-05-13 4:12 ` Michael Schmitz
2009-05-13 4:34 ` Brad Boyer
2009-05-13 8:51 ` Alan Cox
2009-05-13 8:55 ` Geert Uytterhoeven
2009-05-13 23:57 ` Robert Hancock
2009-05-14 0:18 ` FUJITA Tomonori
2009-05-15 5:31 ` Tejun Heo
2009-05-15 11:16 ` Arnd Bergmann
2009-05-15 11:21 ` Tejun Heo
2009-05-15 11:55 ` Arnd Bergmann
2009-05-17 9:00 ` Robert Hancock
2009-05-17 19:38 ` Arnd Bergmann
2009-05-17 20:05 ` Jeff Garzik
2009-05-17 22:45 ` [PATCH] asm-generic: add a dma-mapping.h file Arnd Bergmann
2009-05-18 6:03 ` Geert Uytterhoeven
2009-05-18 8:28 ` Arnd Bergmann
2009-05-18 10:45 ` FUJITA Tomonori
2009-05-18 14:45 ` Arnd Bergmann
2009-05-18 22:44 ` FUJITA Tomonori
2009-05-19 16:22 ` Arnd Bergmann
2009-05-19 17:01 ` Grant Grundler
2009-05-19 17:40 ` Arnd Bergmann
2009-05-19 18:08 ` Grant Grundler
2009-05-22 12:12 ` FUJITA Tomonori
2009-05-22 14:07 ` Arnd Bergmann
2009-05-22 14:38 ` FUJITA Tomonori
2009-05-22 15:05 ` Arnd Bergmann
2009-05-26 4:36 ` FUJITA Tomonori
2009-05-18 22:54 ` Jeff Garzik [this message]
2009-05-18 23:22 ` FUJITA Tomonori
2009-05-18 10:45 ` [PATCH] ata: libata depends on HAS_DMA FUJITA Tomonori
2009-05-13 10:39 ` Arnd Bergmann
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=4A11E739.6080106@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=flar@allandria.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=geert@linux-m68k.org \
--cc=hancockrwd@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitz@biophys.uni-duesseldorf.de \
--cc=takata@linux-m32r.org \
--cc=ysato@users.sourceforge.jp \
/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).