From: Christoph Hellwig <hch@lst.de>
To: Max Filippov <jcmvbkbc@gmail.com>,
Chris Zankel <chris@zankel.net>,
iommu@lists.linux-foundation.org
Cc: linux-xtensa@linux-xtensa.org
Subject: switch xtensa over to the generic DMA remap / uncached segment code
Date: Fri, 1 Nov 2019 15:02:08 -0700 [thread overview]
Message-ID: <20191101220213.28949-1-hch@lst.de> (raw)
Hi all,
this series switches over xtensa to use the generic DMA remap and
uncached code. Xtensa is a little special because it uses an uncached
segment by default, but can still use page table bits for remapping
highmem. To facilitate that there is some major refactoring in the
common DMA code that merges the remapping code into the main direct
mapping alloc / free routines.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2019-11-01 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 22:02 Christoph Hellwig [this message]
2019-11-01 22:02 ` [PATCH 1/5] dma-direct: remove __dma_direct_free_pages Christoph Hellwig
2019-11-01 22:02 ` [PATCH 2/5] dma-direct: remove the dma_handle argument to __dma_direct_alloc_pages Christoph Hellwig
2019-11-01 22:02 ` [PATCH 3/5] dma-direct: provide mmap and get_sgtable method overrides Christoph Hellwig
2019-11-01 22:02 ` [PATCH 4/5] dma-mapping: merge the generic remapping helpers into dma-direct Christoph Hellwig
2019-11-01 22:02 ` [PATCH 5/5] xtensa: use the generic uncached segment support Christoph Hellwig
2019-11-02 3:18 ` switch xtensa over to the generic DMA remap / uncached segment code Max Filippov
2019-11-07 17:44 ` 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=20191101220213.28949-1-hch@lst.de \
--to=hch@lst.de \
--cc=chris@zankel.net \
--cc=iommu@lists.linux-foundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-xtensa@linux-xtensa.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).