From: brian.starkey@arm.com (Brian Starkey)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/3] Add MEMREMAP_WC to fix dma_init_coherent_memory
Date: Fri, 29 Jan 2016 09:32:59 +0000 [thread overview]
Message-ID: <20160129093258.GA695@e106950-lin.cambridge.arm.com> (raw)
In-Reply-To: <cover.1452010802.git.brian.starkey@arm.com>
Hi,
Are there any comments on these? Without them dma-coherent can't be used
on arm64 so it would be good to get them merged if there are no
objections.
I can resend with Michal's ack for patch 2 if needed.
Thanks,
Brian
On Tue, Jan 05, 2016 at 04:41:25PM +0000, Brian Starkey wrote:
>Hi,
>
>This may well have been buried with the holidays. It still applies
>fine on next-20160105, but I notice patch 2 will trivially conflict
>with [2] on some context lines.
>
>As discussed here[1], these patches implement a MEMREMAP_WC flag for
>memremap(), which can be used to obtain writecombine mappings. This
>is then used for setting up dma_coherent_mem regions which use the
>DMA_MEMORY_MAP flag.
>
>Patch 3 makes sure that the appropriate memset function is used
>when zeroing coherent allocations, which fixes an alignment fault on
>arm64.
>
>Best Regards,
>Brian
>
>[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/390857.html
>[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397163.html
>
>Brian Starkey (3):
> memremap: add MEMREMAP_WC flag
> drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP
> drivers: dma-coherent: use memset_io for DMA_MEMORY_IO
>
> drivers/base/dma-coherent.c | 25 ++++++++++++++++++++-----
> include/linux/io.h | 1 +
> kernel/memremap.c | 15 +++++++++++++--
> 3 files changed, 34 insertions(+), 7 deletions(-)
>
>--
>1.7.9.5
>
WARNING: multiple messages have this Message-ID (diff)
From: Brian Starkey <brian.starkey@arm.com>
To: gregkh@linuxfoundation.org
Cc: catalin.marinas@arm.com, dan.j.williams@intel.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Michal Nazarewicz <mina86@mina86.com>
Subject: Re: [RESEND PATCH 0/3] Add MEMREMAP_WC to fix dma_init_coherent_memory
Date: Fri, 29 Jan 2016 09:32:59 +0000 [thread overview]
Message-ID: <20160129093258.GA695@e106950-lin.cambridge.arm.com> (raw)
In-Reply-To: <cover.1452010802.git.brian.starkey@arm.com>
Hi,
Are there any comments on these? Without them dma-coherent can't be used
on arm64 so it would be good to get them merged if there are no
objections.
I can resend with Michal's ack for patch 2 if needed.
Thanks,
Brian
On Tue, Jan 05, 2016 at 04:41:25PM +0000, Brian Starkey wrote:
>Hi,
>
>This may well have been buried with the holidays. It still applies
>fine on next-20160105, but I notice patch 2 will trivially conflict
>with [2] on some context lines.
>
>As discussed here[1], these patches implement a MEMREMAP_WC flag for
>memremap(), which can be used to obtain writecombine mappings. This
>is then used for setting up dma_coherent_mem regions which use the
>DMA_MEMORY_MAP flag.
>
>Patch 3 makes sure that the appropriate memset function is used
>when zeroing coherent allocations, which fixes an alignment fault on
>arm64.
>
>Best Regards,
>Brian
>
>[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-December/390857.html
>[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/397163.html
>
>Brian Starkey (3):
> memremap: add MEMREMAP_WC flag
> drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP
> drivers: dma-coherent: use memset_io for DMA_MEMORY_IO
>
> drivers/base/dma-coherent.c | 25 ++++++++++++++++++++-----
> include/linux/io.h | 1 +
> kernel/memremap.c | 15 +++++++++++++--
> 3 files changed, 34 insertions(+), 7 deletions(-)
>
>--
>1.7.9.5
>
next prev parent reply other threads:[~2016-01-29 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 16:41 [RESEND PATCH 0/3] Add MEMREMAP_WC to fix dma_init_coherent_memory Brian Starkey
2016-01-05 16:41 ` Brian Starkey
2016-01-05 16:41 ` [RESEND PATCH 1/3] memremap: add MEMREMAP_WC flag Brian Starkey
2016-01-05 16:41 ` Brian Starkey
2016-01-05 16:41 ` [RESEND PATCH 2/3] drivers: dma-coherent: use MEMREMAP_WC for DMA_MEMORY_MAP Brian Starkey
2016-01-05 16:41 ` Brian Starkey
2016-01-05 19:02 ` Michal Nazarewicz
2016-01-05 19:02 ` Michal Nazarewicz
2016-01-05 16:41 ` [RESEND PATCH 3/3] drivers: dma-coherent: use memset_io for DMA_MEMORY_IO mappings Brian Starkey
2016-01-05 16:41 ` Brian Starkey
2016-01-29 9:32 ` Brian Starkey [this message]
2016-01-29 9:32 ` [RESEND PATCH 0/3] Add MEMREMAP_WC to fix dma_init_coherent_memory Brian Starkey
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=20160129093258.GA695@e106950-lin.cambridge.arm.com \
--to=brian.starkey@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.