From: Christoph Hellwig <hch@infradead.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Chris Zankel <chris@zankel.net>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xtensa: Fix mmap() support
Date: Thu, 30 Mar 2017 01:45:55 -0700 [thread overview]
Message-ID: <20170330084555.GA13310@infradead.org> (raw)
In-Reply-To: <20170330103032.35558cf3@bbrezillon>
On Thu, Mar 30, 2017 at 10:30:32AM +0200, Boris Brezillon wrote:
> I think I misunderstood what CONFIG_ARCH_NO_COHERENT_DMA_MMAP means.
> My understanding was that, if CONFIG_ARCH_NO_COHERENT_DMA_MMAP is not
> set, the architecture is assumed to be cache-coherent, but re-reading
> the option name I realize you're probably right.
It just says that the architecture did not support dma_common_mmap at
the point in time when I switched all architectures to use the common
dma_ops or implementing the various dma calls. There is no inherent
logic behind the symbol, and if the few remaining architectures could
support it with a bit work the option could just go away.
next prev parent reply other threads:[~2017-03-30 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:20 [PATCH] xtensa: Fix mmap() support Boris Brezillon
2017-03-29 22:48 ` Max Filippov
2017-03-30 8:30 ` Boris Brezillon
2017-03-30 8:45 ` Christoph Hellwig [this message]
2017-03-30 9:05 ` Max Filippov
2017-03-30 10:05 ` Boris Brezillon
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=20170330084555.GA13310@infradead.org \
--to=hch@infradead.org \
--cc=boris.brezillon@free-electrons.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=maxime.ripard@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.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.