linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>,
	Russell King <linux@arm.linux.org.uk>,
	linaro-mm-sig@lists.linaro.org,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: [GIT PULL] DMA-mapping fixes for v3.6
Date: Mon, 03 Sep 2012 13:00:24 +0200	[thread overview]
Message-ID: <1346670024-504-1-git-send-email-m.szyprowski@samsung.com> (raw)

Hi Linus,

I would like to ask for pulling another set of fixes for ARM dma-mapping
subsystem. Commit e9da6e9905e6 replaced custom consistent buffer
remapping code with generic vmalloc areas. It however introduced some
regressions caused by limited support for allocations in atomic context.
This series contains fixes for those regressions. For some subplatforms
the default, pre-allocated pool for atomic allocations turned out to be
too small, so a function for setting its size has been added. Another
set of patches adds support for atomic allocations to IOMMU-aware
DMA-mapping implementation. The last part of this pull request contains
two fixes for Contiguous Memory Allocator, which relax too strict
requirements.

The following changes since commit fea7a08acb13524b47711625eebea40a0ede69a0:

  Linux 3.6-rc3 (2012-08-22 13:29:06 -0700)

are available in the git repository at:

   fixes-for-3.6

for you to fetch changes up to 479ed93a4b98eef03fd8260f7ddc00019221c450:

  ARM: dma-mapping: IOMMU allocates pages from atomic_pool with GFP_ATOMIC (2012-08-28 21:01:07 +0200)

Thanks!

Best regards
Marek Szyprowski
Samsung Poland R&D Center

----------------------------------------------------------------
Patch summary:

Hiroshi Doyu (4):
      ARM: dma-mapping: atomic_pool with struct page **pages
      ARM: dma-mapping: Refactor out to introduce __in_atomic_pool
      ARM: dma-mapping: Introduce __atomic_get_pages() for __iommu_get_pages()
      ARM: dma-mapping: IOMMU allocates pages from atomic_pool with GFP_ATOMIC

Marek Szyprowski (5):
      mm: cma: fix alignment requirements for contiguous regions
      ARM: relax conditions required for enabling Contiguous Memory Allocator
      ARM: DMA-Mapping: add function for setting coherent pool size from platform code
      ARM: DMA-Mapping: print warning when atomic coherent allocation fails
      ARM: Kirkwood: increase atomic coherent pool size

 arch/arm/Kconfig                   |    2 +-
 arch/arm/include/asm/dma-mapping.h |    7 ++
 arch/arm/mach-kirkwood/common.c    |    7 ++
 arch/arm/mm/dma-mapping.c          |  114 ++++++++++++++++++++++++++++++++---
 drivers/base/dma-contiguous.c      |    2 +-
 5 files changed, 120 insertions(+), 12 deletions(-)

                 reply	other threads:[~2012-09-03 11:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1346670024-504-1-git-send-email-m.szyprowski@samsung.com \
    --to=m.szyprowski@samsung.com \
    --cc=arnd@arndb.de \
    --cc=kyungmin.park@samsung.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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).