From: Christoph Hellwig <hch@lst.de>
To: Zhiqiang Hou <Zhiqiang.Hou@nxp.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org, hch@lst.de,
m.szyprowski@samsung.com, robin.murphy@arm.com
Subject: Re: [RFC PATCH] dma: coherent: respect to device 'dma-coherent' property
Date: Sun, 16 Apr 2023 08:30:28 +0200 [thread overview]
Message-ID: <20230416063028.GA6276@lst.de> (raw)
In-Reply-To: <20230414080307.35114-1-Zhiqiang.Hou@nxp.com>
On Fri, Apr 14, 2023 at 04:03:07PM +0800, Zhiqiang Hou wrote:
> From: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
>
> Currently, the coherent DMA memory is always mapped as writecombine
> and uncached, ignored the 'dma-coherent' property in device node,
> this patch is to map the memory as writeback and cached when the
> device has 'dma-coherent' property.
What is the use case here? The somewhat misnamed per-device coherent
memory is intended for small per-device pools of sram or such
used for staging memory.
next prev parent reply other threads:[~2023-04-16 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:03 [RFC PATCH] dma: coherent: respect to device 'dma-coherent' property Zhiqiang Hou
2023-04-16 6:30 ` Christoph Hellwig [this message]
2023-04-17 2:06 ` Z.Q. Hou
2023-04-17 12:27 ` Robin Murphy
2023-04-18 9:55 ` Z.Q. Hou
2023-05-26 0:33 ` Z.Q. Hou
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=20230416063028.GA6276@lst.de \
--to=hch@lst.de \
--cc=Zhiqiang.Hou@nxp.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.