From: "hch@lst.de" <hch@lst.de> To: Alexey Brodkin <Alexey.Brodkin@synopsys.com> Cc: "hch@lst.de" <hch@lst.de>, "deanbo422@gmail.com" <deanbo422@gmail.com>, "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "nios2-dev@lists.rocketboards.org" <nios2-dev@lists.rocketboards.org>, "linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>, "linux-m68k@lists.linux-m68k.org" <linux-m68k@lists.linux-m68k.org>, "linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>, "linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>, "linux-snps-arc@lists.infradead.org" <linux-snps-arc@lists.infradead.org>, "green.hu@gmail.com" <green.hu@gmail.com>, "openrisc@lists.librecores.org" <openrisc@lists.librecores.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH 06/22] arc: use generic dma_noncoherent_ops Date: Thu, 26 Apr 2018 08:45:00 +0200 [thread overview] Message-ID: <20180426064500.GB13895@lst.de> (raw) In-Reply-To: <1524655020.5315.9.camel@synopsys.com> On Wed, Apr 25, 2018 at 11:17:01AM +0000, Alexey Brodkin wrote: > Which is actually strange as I would expect ARC code to be built by bots. I don't think I got any notification. Thank for the fixes! I think I found the bug, based on the fact that so far all tests for architectures that also need a cache op for device to cpu transitions failed. I did a stupid typo when changing kconfig symbols, so please try the patch below. > > static int l2_line_sz; > static int ioc_exists; > -int slc_enable = 1, ioc_enable = 1; > +int slc_enable = 1, ioc_enable = 0; Hmm. It seems if ioc_enable is 0 we should simply be using dma_direct_ops on arc, but that is a different discussion. --- diff --git a/lib/dma-noncoherent.c b/lib/dma-noncoherent.c index f4b8532c20ac..a2c192b3508d 100644 --- a/lib/dma-noncoherent.c +++ b/lib/dma-noncoherent.c @@ -48,7 +48,7 @@ static int dma_noncoherent_map_sg(struct device *dev, struct scatterlist *sgl, return nents; } -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU static void dma_noncoherent_sync_single_for_cpu(struct device *dev, dma_addr_t addr, size_t size, enum dma_data_direction dir) { @@ -88,7 +88,7 @@ const struct dma_map_ops dma_noncoherent_ops = { .sync_sg_for_device = dma_noncoherent_sync_sg_for_device, .map_page = dma_noncoherent_map_page, .map_sg = dma_noncoherent_map_sg, -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU .sync_single_for_cpu = dma_noncoherent_sync_single_for_cpu, .sync_sg_for_cpu = dma_noncoherent_sync_sg_for_cpu, .unmap_page = dma_noncoherent_unmap_page,
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de> To: Alexey Brodkin <Alexey.Brodkin@synopsys.com> Cc: "hch@lst.de" <hch@lst.de>, "deanbo422@gmail.com" <deanbo422@gmail.com>, "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "nios2-dev@lists.rocketboards.org" <nios2-dev@lists.rocketboards.org>, "linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>, "linux-m68k@lists.linux-m68k.org" <linux-m68k@lists.linux-m68k.org>, "linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>, "linux-hexagon@vger.kernel.org" <linux-hexagon@vger.kernel.org>, "linux-snps-arc@lists.infradead.org" <linux-snps-arc@lists.infradead.org>, "green.hu@gmail.com" <green.hu@gmail.com>, "openrisc@lists.librecores.org" <openrisc@lists.librecores.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "monstr@monstr.eu" <monstr@monstr.eu>, "linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>, "linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>, "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>, "sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org> Subject: Re: [PATCH 06/22] arc: use generic dma_noncoherent_ops Date: Thu, 26 Apr 2018 08:45:00 +0200 [thread overview] Message-ID: <20180426064500.GB13895@lst.de> (raw) Message-ID: <20180426064500.NMSsdxA9ZQiHQ6pUbFfGUF3bjajKy_iS-qAVi6vXHnA@z> (raw) In-Reply-To: <1524655020.5315.9.camel@synopsys.com> On Wed, Apr 25, 2018 at 11:17:01AM +0000, Alexey Brodkin wrote: > Which is actually strange as I would expect ARC code to be built by bots. I don't think I got any notification. Thank for the fixes! I think I found the bug, based on the fact that so far all tests for architectures that also need a cache op for device to cpu transitions failed. I did a stupid typo when changing kconfig symbols, so please try the patch below. > > static int l2_line_sz; > static int ioc_exists; > -int slc_enable = 1, ioc_enable = 1; > +int slc_enable = 1, ioc_enable = 0; Hmm. It seems if ioc_enable is 0 we should simply be using dma_direct_ops on arc, but that is a different discussion. --- diff --git a/lib/dma-noncoherent.c b/lib/dma-noncoherent.c index f4b8532c20ac..a2c192b3508d 100644 --- a/lib/dma-noncoherent.c +++ b/lib/dma-noncoherent.c @@ -48,7 +48,7 @@ static int dma_noncoherent_map_sg(struct device *dev, struct scatterlist *sgl, return nents; } -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU static void dma_noncoherent_sync_single_for_cpu(struct device *dev, dma_addr_t addr, size_t size, enum dma_data_direction dir) { @@ -88,7 +88,7 @@ const struct dma_map_ops dma_noncoherent_ops = { .sync_sg_for_device = dma_noncoherent_sync_sg_for_device, .map_page = dma_noncoherent_map_page, .map_sg = dma_noncoherent_map_sg, -#ifdef CONFIG_DMA_NONCOHERENT_SYNC_FOR_CPU +#ifdef CONFIG_ARCH_HAS_SYNC_DMA_FOR_CPU .sync_single_for_cpu = dma_noncoherent_sync_single_for_cpu, .sync_sg_for_cpu = dma_noncoherent_sync_sg_for_cpu, .unmap_page = dma_noncoherent_unmap_page,
next prev parent reply other threads:[~2018-04-26 6:45 UTC|newest] Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-20 8:02 (unknown), Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 01/22] dma-debug: move initialization to common code Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 10:23 ` Robin Murphy 2018-04-20 10:23 ` Robin Murphy 2018-04-24 7:35 ` Christoph Hellwig 2018-04-24 7:35 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 02/22] dma-mapping: simplify Kconfig dependencies Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 03/22] dma-mapping: provide a generic dma-noncoherent implementation Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 04/22] alpha: use dma_direct_ops for jensen Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 05/22] alpha: simplify get_arch_dma_ops Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 06/22] arc: use generic dma_noncoherent_ops Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-25 11:17 ` Alexey Brodkin 2018-04-25 11:17 ` Alexey Brodkin 2018-04-26 6:45 ` hch [this message] 2018-04-26 6:45 ` hch 2018-04-26 8:25 ` hch 2018-04-26 8:25 ` hch 2018-04-20 8:02 ` [PATCH 07/22] arm-nommu: " Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:02 ` [PATCH 08/22] c6x: " Christoph Hellwig 2018-04-20 8:02 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 09/22] hexagon: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 10/22] m68k: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 11/22] microblaze: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 12/22] microblaze: remove the consistent_sync and consistent_sync_page Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 13/22] nds32: use generic dma_noncoherent_ops Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-23 6:49 ` Greentime Hu 2018-04-23 6:49 ` Greentime Hu 2018-04-23 8:09 ` Michael Schmitz 2018-04-23 11:03 ` Greentime Hu 2018-04-24 19:16 ` Christoph Hellwig 2018-04-24 19:16 ` Christoph Hellwig 2018-04-25 1:43 ` Greentime Hu 2018-04-25 1:43 ` Greentime Hu 2018-04-25 6:40 ` Christoph Hellwig 2018-04-25 6:40 ` Christoph Hellwig 2018-04-25 12:25 ` Greentime Hu 2018-04-25 12:25 ` Greentime Hu 2018-04-26 6:42 ` Christoph Hellwig 2018-04-26 6:42 ` Christoph Hellwig 2018-04-26 8:06 ` Greentime Hu 2018-04-26 8:06 ` Greentime Hu 2018-04-26 8:24 ` Christoph Hellwig 2018-04-26 8:24 ` Christoph Hellwig 2018-04-26 9:39 ` Greentime Hu 2018-04-26 9:39 ` Greentime Hu 2018-04-20 8:03 ` [PATCH 14/22] nios2: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 15/22] openrisc: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 16/22] sh: simplify get_arch_dma_ops Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 17/22] sh: introduce a sh_cacheop_vaddr helper Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 18/22] sh: use dma_direct_ops for the CONFIG_DMA_COHERENT case Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 19/22] sh: use generic dma_noncoherent_ops Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 20/22] xtensa: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 21/22] sparc: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-20 8:03 ` [PATCH 22/22] parisc: " Christoph Hellwig 2018-04-20 8:03 ` Christoph Hellwig 2018-04-21 17:43 ` Helge Deller 2018-04-21 17:43 ` Helge Deller 2018-04-21 21:52 ` James Bottomley 2018-04-21 21:52 ` James Bottomley 2018-04-25 7:21 ` Christoph Hellwig 2018-04-25 7:21 ` Christoph Hellwig 2018-04-25 21:07 ` Helge Deller 2018-04-25 21:07 ` Helge Deller 2018-04-21 21:42 ` James Bottomley 2018-04-21 21:42 ` James Bottomley 2018-04-24 8:20 ` Christoph Hellwig 2018-04-24 8:20 ` Christoph Hellwig
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=20180426064500.GB13895@lst.de \ --to=hch@lst.de \ --cc=Alexey.Brodkin@synopsys.com \ --cc=deanbo422@gmail.com \ --cc=green.hu@gmail.com \ --cc=linux-alpha@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-hexagon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-m68k@lists.linux-m68k.org \ --cc=linux-sh@vger.kernel.org \ --cc=linux-snps-arc@lists.infradead.org \ --cc=linux-xtensa@linux-xtensa.org \ --cc=nios2-dev@lists.rocketboards.org \ --cc=openrisc@lists.librecores.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: linkBe 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).