From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code
Date: Tue, 25 Jun 2019 14:28:08 +0200 [thread overview]
Message-ID: <20190625122808.GB4421@lst.de> (raw)
In-Reply-To: <3eb32e0b-5aa4-fe1e-e581-038750e11cef@gmx.de>
On Tue, Jun 25, 2019 at 02:23:45PM +0200, Helge Deller wrote:
> On 14.06.19 16:44, Christoph Hellwig wrote:
> > Only call into arch_dma_alloc if we require an uncached mapping,
> > and remove the parisc code manually doing normal cached
> > DMA_ATTR_NON_CONSISTENT allocations.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Acked-by: Helge Deller <deller@gmx.de> # parisc
>
> Boot-tested 32-bit kernel on PCX-L and PCX-W2 machines (although
> the patches don't cleanly apply any longer against git head).
The series was against the dma-mapping tree, which might have diverged
a bit already.
Thanks for testing!
next prev parent reply other threads:[~2019-06-25 12:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 14:44 [OpenRISC] handle "special" dma allocation in common code Christoph Hellwig
2019-06-14 14:44 ` [OpenRISC] [PATCH 1/7] arm-nommu: remove the partial DMA_ATTR_NON_CONSISTENT support Christoph Hellwig
2019-06-24 14:23 ` Vladimir Murzin
2019-06-25 6:13 ` Christoph Hellwig
2019-06-14 14:44 ` [OpenRISC] [PATCH 2/7] arc: " Christoph Hellwig
2019-06-14 14:44 ` [OpenRISC] [PATCH 3/7] openrisc: " Christoph Hellwig
2019-06-16 9:17 ` Stafford Horne
2019-06-14 14:44 ` [OpenRISC] [PATCH 4/7] dma-mapping: add a dma_alloc_need_uncached helper Christoph Hellwig
2019-06-14 14:44 ` [OpenRISC] [PATCH 5/7] dma-direct: handle DMA_ATTR_NON_CONSISTENT in common code Christoph Hellwig
2019-06-25 6:11 ` Christoph Hellwig
2019-06-25 12:23 ` Helge Deller
2019-06-25 12:28 ` Christoph Hellwig [this message]
2019-06-14 14:44 ` [OpenRISC] [PATCH 6/7] dma-direct: handle DMA_ATTR_NO_KERNEL_MAPPING " Christoph Hellwig
2019-06-29 15:09 ` Guenter Roeck
2019-06-14 14:44 ` [OpenRISC] [PATCH 7/7] arc: use the generic remapping allocator for coherent DMA allocations Christoph Hellwig
2019-06-14 18:05 ` Eugeniy Paltsev
2019-06-15 8:35 ` hch
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=20190625122808.GB4421@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).