From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: rubini@gnudd.com, hch@infradead.org, linux-kernel@vger.kernel.org
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-pci@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [PATCH v3 0/2] x86: Get rid of custom DMA functions
Date: Thu, 7 Nov 2019 16:06:43 +0100 [thread overview]
Message-ID: <20191107150646.13485-1-nsaenzjulienne@suse.de> (raw)
sta2x11 is the only x86 device that depends custom DMA direct functions.
It turns out it can be made standard by carefully setting the device's
DMA masks and offset.
Originally only patch #2 was sent but I realised patch #1 is also
needed, which is a good addition as it's also a prerequisite to get
proper DMA support on the Raspberry Pi 4[1].
[1] https://lkml.org/lkml/2019/10/15/523
---
Changes since v2:
- cleanup dma-direct.h
Changes since v1:
- Small cleanups in sta2x11-fixup.x
- add patch checking DMA addresses lower bounds
Nicolas Saenz Julienne (2):
dma-direct: check for overflows on 32 bit DMA addresses
x86/PCI: sta2x11: use default DMA address translation
arch/x86/Kconfig | 1 -
arch/x86/include/asm/device.h | 3 -
arch/x86/include/asm/dma-direct.h | 9 --
arch/x86/pci/sta2x11-fixup.c | 135 ++++++------------------------
include/linux/dma-direct.h | 12 ++-
5 files changed, 36 insertions(+), 124 deletions(-)
delete mode 100644 arch/x86/include/asm/dma-direct.h
--
2.23.0
next reply other threads:[~2019-11-07 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 15:06 Nicolas Saenz Julienne [this message]
2019-11-07 15:06 ` [PATCH v3 1/2] dma-direct: check for overflows on 32 bit DMA addresses Nicolas Saenz Julienne
2019-11-07 15:06 ` [PATCH v3 2/2] x86/PCI: sta2x11: use default DMA address translation Nicolas Saenz Julienne
2019-11-13 18:54 ` Borislav Petkov
2019-11-14 7:29 ` 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=20191107150646.13485-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=rubini@gnudd.com \
/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).