From: Laura Abbott <lauraa@codeaurora.org>
To: James Hogan <james.hogan@imgtec.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Will Deacon <will.deacon@arm.com>,
Russell King <linux@arm.linux.org.uk>,
David Riley <davidriley@chromium.org>,
ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Ritesh Harjain <ritesh.harjani@gmail.com>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-next@vger.kernel.org
Subject: Re: [PATCHv7 3/5] common: dma-mapping: Introduce common remapping functions
Date: Tue, 26 Aug 2014 09:58:43 -0700 [thread overview]
Message-ID: <53FCBCC3.5040901@codeaurora.org> (raw)
In-Reply-To: <CAAG0J99=wrz4+c49HeDvL0W9rDZKk2HNLdVtHv4ZJxU4-OjewA@mail.gmail.com>
On 8/26/2014 3:05 AM, James Hogan wrote:
> On 12 August 2014 00:40, Laura Abbott <lauraa@codeaurora.org> wrote:
>>
>> For architectures without coherent DMA, memory for DMA may
>> need to be remapped with coherent attributes. Factor out
>> the the remapping code from arm and put it in a
>> common location to reduce code duplication.
>>
>> As part of this, the arm APIs are now migrated away from
>> ioremap_page_range to the common APIs which use map_vm_area for remapping.
>> This should be an equivalent change and using map_vm_area is more
>> correct as ioremap_page_range is intended to bring in io addresses
>> into the cpu space and not regular kernel managed memory.
>>
>> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
>
> This commit in linux-next () breaks the build for metag:
>
> drivers/base/dma-mapping.c: In function a??dma_common_contiguous_remapa??:
> drivers/base/dma-mapping.c:294: error: implicit declaration of
> function a??dma_common_pages_remapa??
> drivers/base/dma-mapping.c:294: warning: assignment makes pointer from
> integer without a cast
> drivers/base/dma-mapping.c: At top level:
> drivers/base/dma-mapping.c:308: error: conflicting types for
> a??dma_common_pages_remapa??
> drivers/base/dma-mapping.c:294: error: previous implicit declaration
> of a??dma_common_pages_remapa?? was here
>
> Looks like metag isn't alone either:
>
> $ git grep -L dma-mapping-common arch/*/include/asm/dma-mapping.h
> arch/arc/include/asm/dma-mapping.h
> arch/avr32/include/asm/dma-mapping.h
> arch/blackfin/include/asm/dma-mapping.h
> arch/c6x/include/asm/dma-mapping.h
> arch/cris/include/asm/dma-mapping.h
> arch/frv/include/asm/dma-mapping.h
> arch/m68k/include/asm/dma-mapping.h
> arch/metag/include/asm/dma-mapping.h
> arch/mn10300/include/asm/dma-mapping.h
> arch/parisc/include/asm/dma-mapping.h
> arch/xtensa/include/asm/dma-mapping.h
>
> I've checked a couple of these arches (blackfin, xtensa) which don't
> include dma-mapping-common.h and their builds seem to be broken too.
>
> Cheers
> James
>
Thanks for the report. Would you mind giving the following patch
a test (this is theoretical only but I think it should work)
-----8<------
next prev parent reply other threads:[~2014-08-26 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 23:40 [PATCHv7 0/5] DMA Atomic pool for arm64 Laura Abbott
2014-08-11 23:40 ` [PATCHv7 1/5] lib/genalloc.c: Add power aligned algorithm Laura Abbott
2014-08-11 23:40 ` [PATCHv7 2/5] lib/genalloc.c: Add genpool range check function Laura Abbott
2014-08-11 23:40 ` [PATCHv7 3/5] common: dma-mapping: Introduce common remapping functions Laura Abbott
2014-08-26 10:05 ` James Hogan
2014-08-26 16:58 ` Laura Abbott [this message]
2014-08-27 9:30 ` James Hogan
2014-08-27 21:01 ` Mark Salter
2014-08-11 23:40 ` [PATCHv7 4/5] arm: use genalloc for the atomic pool Laura Abbott
2014-08-11 23:40 ` [PATCHv7 5/5] arm64: Add atomic pool for non-coherent and CMA allocations Laura Abbott
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=53FCBCC3.5040901@codeaurora.org \
--to=lauraa@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=davidriley@chromium.org \
--cc=james.hogan@imgtec.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ritesh.harjani@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=will.deacon@arm.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).