iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org,
	Russell King <linux@armlinux.org.uk>,
	Santosh Shilimkar <ssantosh@kernel.org>
Cc: devicetree@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	linux-sh@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-acpi@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Jim Quinlan <james.quinlan@broadcom.com>,
	linux-pci@vger.kernel.org,
	Nathan Chancellor <natechancellor@gmail.com>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: support range based offsets in dma-direct
Date: Thu, 10 Sep 2020 07:40:35 +0200	[thread overview]
Message-ID: <20200910054038.324517-1-hch@lst.de> (raw)

Hi all,

this series adds range-based offsets to the dma-direct implementation.  The
guts of the change are a patch from Jim with some modifications from me,
but to do it nicely we need to ARM patches to prepare for it as well.

Diffstat:
 arch/arm/common/dmabounce.c                        |    2 
 arch/arm/include/asm/dma-direct.h                  |   69 +++++++++++++++++
 arch/arm/include/asm/dma-mapping.h                 |   70 ------------------
 arch/arm/mach-keystone/keystone.c                  |   21 +++--
 arch/sh/drivers/pci/pcie-sh7786.c                  |    9 +-
 arch/x86/pci/sta2x11-fixup.c                       |    6 +
 drivers/acpi/arm64/iort.c                          |    6 +
 drivers/base/core.c                                |    2 
 drivers/gpu/drm/sun4i/sun4i_backend.c              |    8 +-
 drivers/iommu/io-pgtable-arm.c                     |    2 
 drivers/media/platform/sunxi/sun4i-csi/sun4i_csi.c |    9 ++
 drivers/media/platform/sunxi/sun6i-csi/sun6i_csi.c |   11 ++
 drivers/of/address.c                               |   73 ++++++++----------
 drivers/of/device.c                                |   44 +++++++----
 drivers/of/of_private.h                            |   11 +-
 drivers/of/unittest.c                              |   34 ++++++--
 drivers/remoteproc/remoteproc_core.c               |    4 -
 drivers/staging/media/sunxi/cedrus/cedrus_hw.c     |   10 ++
 drivers/usb/core/message.c                         |    5 -
 drivers/usb/core/usb.c                             |    3 
 include/linux/device.h                             |    4 -
 include/linux/dma-direct.h                         |   52 +++++++++++--
 include/linux/dma-mapping.h                        |   19 ++++
 kernel/dma/coherent.c                              |    7 -
 kernel/dma/direct.c                                |   81 ++++++++++++++++++++-
 25 files changed, 373 insertions(+), 189 deletions(-)
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2020-09-10  5:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  5:40 Christoph Hellwig [this message]
2020-09-10  5:40 ` [PATCH 1/3] ARM/dma-mapping: move various helpers from dma-mapping.h to dma-direct.h Christoph Hellwig
2020-09-10 18:02   ` Robin Murphy
2020-09-11  6:25     ` Christoph Hellwig
2020-09-10  5:40 ` [PATCH 2/3] ARM/keystone: move the DMA offset handling under ifdef CONFIG_ARM_LPAE Christoph Hellwig
2020-09-11 11:12   ` Robin Murphy
2020-09-11 11:15   ` Russell King - ARM Linux admin
2020-09-11 11:27     ` Robin Murphy
2020-09-11 18:00     ` santosh.shilimkar
2020-09-10  5:40 ` [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset Christoph Hellwig
2020-09-10  7:53   ` Greg KH
2020-09-10  9:13     ` Christoph Hellwig
2020-09-10 16:12       ` Greg KH
2020-09-11 16:12   ` Robin Murphy
2020-09-12  6:46     ` 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=20200910054038.324517-1-hch@lst.de \
    --to=hch@lst.de \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=james.quinlan@broadcom.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=natechancellor@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=ssantosh@kernel.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).