mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Christoph Hellwig <hch@lst.de>, <iommu@lists.linux-foundation.org>
Cc: <linux-arch@vger.kernel.org>, <linux-xtensa@linux-xtensa.org>,
	"Michal Simek" <monstr@monstr.eu>,
	Vincent Chen <deanbo422@gmail.com>, <linux-c6x-dev@linux-c6x.org>,
	<linux-parisc@vger.kernel.org>, <linux-sh@vger.kernel.org>,
	<linux-hexagon@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-m68k@lists.linux-m68k.org>,
	<openrisc@lists.librecores.org>,
	Greentime Hu <green.hu@gmail.com>, <linux-alpha@vger.kernel.org>,
	<sparclinux@vger.kernel.org>, <nios2-dev@lists.rocketboards.org>,
	<linux-snps-arc@lists.infradead.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 04/20] arm-nommu: use generic dma_noncoherent_ops
Date: Fri, 11 May 2018 14:56:16 +0100	[thread overview]
Message-ID: <73603c68-da05-22bd-efab-d0387a98225d@huawei.com> (raw)
In-Reply-To: <20180511075945.16548-5-hch@lst.de>

On 11/05/2018 08:59, Christoph Hellwig wrote:
> Switch to the generic noncoherent direct mapping implementation for
> the nommu dma map implementation.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  arch/arc/Kconfig                |   1 +
>  arch/arm/Kconfig                |   4 +
>  arch/arm/mm/dma-mapping-nommu.c | 139 +++++---------------------------
>  3 files changed, 23 insertions(+), 121 deletions(-)
>
> diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig
> index 89d47eac18b2..3a492a9aeaad 100644
> --- a/arch/arc/Kconfig
> +++ b/arch/arc/Kconfig
> @@ -9,6 +9,7 @@
>  config ARC
>  	def_bool y
>  	select ARC_TIMERS
> +	select ARCH_HAS_SYNC_DMA_FOR_DEVICE
>  	select ARCH_HAS_SYNC_DMA_FOR_CPU
>  	select ARCH_HAS_SYNC_DMA_FOR_DEVICE

I guess that this arc change is here by accident, no? And isn't 
ARCH_HAS_SYNC_DMA_FOR_DEVICE already selected (by 3/20)?

>  	select ARCH_HAS_SG_CHAIN
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index c43f5bb55ac8..76ddd0064f87 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig

  parent reply	other threads:[~2018-05-11 13:56 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  7:59 common non-cache coherent direct dma mapping ops Christoph Hellwig
2018-05-11  7:59 ` [PATCH 01/20] dma-mapping: simplify Kconfig dependencies Christoph Hellwig
2018-05-11  7:59 ` [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation Christoph Hellwig
2018-05-18 13:03   ` Alexey Brodkin
2018-05-18 13:27     ` hch
2018-05-18 14:13       ` Alexey Brodkin
2018-05-18 17:28       ` Vineet Gupta
2018-05-18 17:20     ` dma_sync_*_for_cpu and direction=TO_DEVICE (was Re: [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation) Vineet Gupta
2018-05-18 17:50       ` Russell King - ARM Linux
2018-05-18 19:57         ` Alexey Brodkin
2018-05-18 21:33           ` Russell King - ARM Linux
2018-05-18 20:35         ` Vineet Gupta
2018-05-18 21:55           ` Russell King - ARM Linux
2018-05-18 20:05     ` [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation Helge Deller
2018-05-19  6:38       ` hch
2018-05-11  7:59 ` [PATCH 03/20] arc: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11 12:44   ` Alexey Brodkin
2018-05-11  7:59 ` [PATCH 04/20] arm-nommu: " Christoph Hellwig
2018-05-11  9:11   ` Russell King - ARM Linux
2018-05-22 11:53     ` Christoph Hellwig
2018-05-11 13:56   ` John Garry [this message]
2018-05-11  7:59 ` [PATCH 05/20] c6x: " Christoph Hellwig
2018-05-15  0:25   ` [Linux-c6x-dev] " Mark Salter
2018-05-11  7:59 ` [PATCH 06/20] hexagon: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 07/20] m68k: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 08/20] microblaze: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 09/20] microblaze: remove the consistent_sync and consistent_sync_page Christoph Hellwig
2018-05-11  7:59 ` [PATCH 10/20] nds32: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11  7:59 ` [PATCH 11/20] nios2: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 12/20] openrisc: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 13/20] sh: simplify get_arch_dma_ops Christoph Hellwig
2018-05-11  7:59 ` [PATCH 14/20] sh: introduce a sh_cacheop_vaddr helper Christoph Hellwig
2018-05-11  7:59 ` [PATCH 15/20] sh: use dma_direct_ops for the CONFIG_DMA_COHERENT case Christoph Hellwig
2018-05-11  7:59 ` [PATCH 16/20] mm: split arch/sh/mm/consistent.c Christoph Hellwig
2018-05-11  7:59 ` [PATCH 17/20] sh: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11  7:59 ` [PATCH 18/20] xtensa: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 19/20] sparc: " Christoph Hellwig
2018-05-11  7:59 ` [PATCH 20/20] parisc: " Christoph Hellwig
2018-05-13 13:26 ` common non-cache coherent direct dma mapping ops Helge Deller

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=73603c68-da05-22bd-efab-d0387a98225d@huawei.com \
    --to=john.garry@huawei.com \
    --cc=deanbo422@gmail.com \
    --cc=green.hu@gmail.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=monstr@monstr.eu \
    --cc=nios2-dev@lists.rocketboards.org \
    --cc=openrisc@lists.librecores.org \
    --cc=sparclinux@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

all inboxes | Powered by JetHome®