linux-openrisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hch@lst.de <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent	implementation
Date: Sat, 19 May 2018 08:38:57 +0200	[thread overview]
Message-ID: <20180519063857.GA18076@lst.de> (raw)
In-Reply-To: <0c5d27e9-2799-eb38-8b09-47a04c48b5c7@gmx.de>

On Fri, May 18, 2018 at 10:05:51PM +0200, Helge Deller wrote:
> This patch seems to fix the dma issues I faced on my 32bit B160L parisc box.
> 
> So it leaves only one open issue on parisc:
> Now every 32 bit parisc system is unnecessarily non-coherent.

I diagree with those comments, let me resend the refactored patch
to make it more clear.

  reply	other threads:[~2018-05-19  6:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  7:59 [OpenRISC] common non-cache coherent direct dma mapping ops Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 01/20] dma-mapping: simplify Kconfig dependencies Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation Christoph Hellwig
     [not found]   ` <bad125dff49f6e49c895e818c9d1abb346a46e8e.camel@synopsys.com>
2018-05-18 13:27     ` hch
     [not found]     ` <5ac5b1e3-9b96-9c7c-4dfe-f65be45ec179@synopsys.com>
2018-05-18 17:50       ` [OpenRISC] dma_sync_*_for_cpu and direction=TO_DEVICE (was Re: [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation) Russell King - ARM Linux
     [not found]         ` <182840dedb4890a88c672b1c5d556920bf89a8fb.camel@synopsys.com>
2018-05-18 21:33           ` Russell King - ARM Linux
     [not found]         ` <cecfe6bd-ef1f-1e25-bfcf-992d1f828efb@synopsys.com>
2018-05-18 21:55           ` Russell King - ARM Linux
2018-05-18 20:05     ` [OpenRISC] [PATCH 02/20] dma-mapping: provide a generic dma-noncoherent implementation Helge Deller
2018-05-19  6:38       ` hch [this message]
2018-05-11  7:59 ` [OpenRISC] [PATCH 03/20] arc: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [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
2018-05-11  7:59 ` [OpenRISC] [PATCH 05/20] c6x: " Christoph Hellwig
2018-05-15  0:25   ` [OpenRISC] [Linux-c6x-dev] " Mark Salter
2018-05-11  7:59 ` [OpenRISC] [PATCH 06/20] hexagon: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 07/20] m68k: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 08/20] microblaze: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 09/20] microblaze: remove the consistent_sync and consistent_sync_page Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 10/20] nds32: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 11/20] nios2: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 12/20] openrisc: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 13/20] sh: simplify get_arch_dma_ops Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 14/20] sh: introduce a sh_cacheop_vaddr helper Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 15/20] sh: use dma_direct_ops for the CONFIG_DMA_COHERENT case Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 16/20] mm: split arch/sh/mm/consistent.c Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 17/20] sh: use generic dma_noncoherent_ops Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 18/20] xtensa: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 19/20] sparc: " Christoph Hellwig
2018-05-11  7:59 ` [OpenRISC] [PATCH 20/20] parisc: " Christoph Hellwig
2018-05-13 13:26 ` [OpenRISC] 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=20180519063857.GA18076@lst.de \
    --to=hch@lst.de \
    --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: 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).