linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH -mm 0/8] unify dma_addr_t typedef (CONFIG_ARCH_DMA_ADDR_T_64BIT)
Date: Fri, 3 Sep 2010 15:09:48 -0700	[thread overview]
Message-ID: <20100903150948.4b612498.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100903094753S.fujita.tomonori@lab.ntt.co.jp>

On Fri, 3 Sep 2010 09:51:31 +0900
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:

> There are about twenty architectures have the own dma_addr_t typedef
> because include/asm-generic/types.h can't be perfect (some of them can
> use it though):
> 
> #ifndef dma_addr_t
> #ifdef CONFIG_PHYS_ADDR_T_64BIT
> typedef u64 dma_addr_t;
> #else
> typedef u32 dma_addr_t;
> #endif /* CONFIG_PHYS_ADDR_T_64BIT */
> #endif /* dma_addr_t */
> 
> Another problem is that there is a way to determine if dma_addr_t is
> 64-bit. We see hopeless tricks like the following:
> 
> #if (defined(__i386__) && defined(CONFIG_HIGHMEM64G)) || defined(__x86_64__) || defined (__ia64__) || defined(__alpha__) || defined(__mips64__) || (defined(__mips__) && defined(CONFIG_HIGHMEM) && defined(CONFIG_64BIT_PHYS_ADDR))
> 
> This clean up the mess with introducing CONFIG_ARCH_DMA_ADDR_T_64BIT
> define (like CONFIG_ARCH_PHYS_ADDR_T_64BIT).
> 
> If architecture needs 64bit dma_addr_t, it must enable
> CONFIG_ARCH_DMA_ADDR_T_64BIT.
> 
> The summary are:
> 
> - always 64bit
> -- alpha
> -- ia64
> -- tile
> 
> - conditionally 64bit
> -- x86
> -- mips
> -- powerpc
> -- s390
> 
> - always 32bit
> -- arm
> -- avr32
> -- cris
> -- frv
> -- h8300
> -- m32r
> -- m68k
> -- mn10300
> -- parisc
> -- xtensa
> -- sparc
> -- blackfin
> -- microblaze
> -- score
> -- sh

Am I correct in believing that we can merge the first seven patches
into arch trees at any time and, once they are all merged, patch 8/8
can then go into mainline?

  parent reply	other threads:[~2010-09-03 22:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  0:51 [PATCH -mm 0/8] unify dma_addr_t typedef (CONFIG_ARCH_DMA_ADDR_T_64BIT) FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 1/8] x86: enable ARCH_DMA_ADDR_T_64BIT with X86_64 || HIGHMEM64G FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 2/8] alpha: enable ARCH_DMA_ADDR_T_64BIT FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 3/8] ia64: " FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 4/8] mips: enable ARCH_DMA_ADDR_T_64BIT with (HIGHMEM && 64BIT_PHYS_ADDR) || 64BIT FUJITA Tomonori
2010-09-03  0:49   ` FUJITA Tomonori
2010-09-20 13:34   ` Ralf Baechle
2010-09-22  9:18     ` FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 5/8] powerpc: enable ARCH_DMA_ADDR_T_64BIT with ARCH_PHYS_ADDR_T_64BIT FUJITA Tomonori
2010-09-03  0:49   ` FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 6/8] s390: enable ARCH_DMA_ADDR_T_64BIT with 64BIT FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 7/8] tile: enable ARCH_DMA_ADDR_T_64BIT FUJITA Tomonori
2010-09-03  0:49   ` FUJITA Tomonori
2010-09-03  0:49 ` [PATCH -mm 8/8] add the common dma_addr_t typedef to include/linux/types.h FUJITA Tomonori
2010-09-03  0:49   ` FUJITA Tomonori
2010-09-03 12:19   ` Arnd Bergmann
2010-09-03 12:19     ` Arnd Bergmann
     [not found] ` <5uMrkKwSLHA.6664@exchange1.tad.internal.tilera.com>
2010-09-03  1:09   ` [PATCH -mm 7/8] tile: enable ARCH_DMA_ADDR_T_64BIT Chris Metcalf
2010-09-03 12:31     ` Chris Metcalf
2010-09-03 22:09 ` Andrew Morton [this message]
2010-09-04  6:58   ` [PATCH -mm 0/8] unify dma_addr_t typedef (CONFIG_ARCH_DMA_ADDR_T_64BIT) FUJITA Tomonori

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=20100903150948.4b612498.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).