iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Li <gavinli@thegavinli.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
	Robin Murphy <robin.murphy@arm.com>,
	Gavin Li <git@thegavinli.com>
Subject: Re: [PATCH v1] dma-mapping: normal memory for mmap() on coherent architectures
Date: Fri, 2 Aug 2019 23:35:48 -0700	[thread overview]
Message-ID: <CA+GxvY5EzTOXWSn_nKb2=v2Lzy6kKBvd+LfWpeNF5o2iD1E6Rg@mail.gmail.com> (raw)
In-Reply-To: <20190803062333.GC29348@lst.de>

Ah, seems like it wasn't as simple of a fix as I thought :)

I intended to use dma_mmap_coherent() in the usbfs driver
(drivers/usb/core/devio.c) because its mmap() was broken on arm64 and
all the other noncoherent DMA architectures.

Patch here: https://www.spinics.net/lists/linux-usb/msg183148.html
More info: https://www.spinics.net/lists/linux-usb/msg183180.html

On Fri, Aug 2, 2019 at 11:23 PM Christoph Hellwig <hch@lst.de> wrote:
>
> See the discussion at:
>
> https://lists.linuxfoundation.org/pipermail/iommu/2019-August/037716.html
>
> Just curious, what driver do you use that uses dma_mmap_coherent on
> x86?
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-08-03  6:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 18:07 [PATCH v1] dma-mapping: normal memory for mmap() on coherent architectures gavinli
2019-08-03  6:23 ` Christoph Hellwig
2019-08-03  6:35   ` Gavin Li [this message]
2019-08-03  6:39     ` Christoph Hellwig
2020-10-28 11:39   ` Oded Gabbay
2020-10-28 17:31     ` Christoph Hellwig
2020-10-28 17:38       ` Oded Gabbay
2020-10-28 17:39         ` Christoph Hellwig
2020-10-28 19:33           ` Oded Gabbay

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='CA+GxvY5EzTOXWSn_nKb2=v2Lzy6kKBvd+LfWpeNF5o2iD1E6Rg@mail.gmail.com' \
    --to=gavinli@thegavinli.com \
    --cc=git@thegavinli.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=robin.murphy@arm.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).