From: Christoph Hellwig <hch@lst.de>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org
Subject: dma_declare_coherent_memory on main memory
Date: Fri, 7 Dec 2018 16:34:32 +0100 [thread overview]
Message-ID: <20181207153432.GA24917@lst.de> (raw)
Hi all,
the ARM imx27/31 ports and various sh boards use
dma_declare_coherent_memory on main memory taken from the memblock
allocator.
Is there any good reason these couldn't be switched to CMA areas?
Getting rid of these magic dma_declare_coherent_memory area would
help making the dma allocator a lot simpler.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: iommu@lists.linux-foundation.org, linux-sh@vger.kernel.org,
linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: dma_declare_coherent_memory on main memory
Date: Fri, 07 Dec 2018 15:34:32 +0000 [thread overview]
Message-ID: <20181207153432.GA24917@lst.de> (raw)
Hi all,
the ARM imx27/31 ports and various sh boards use
dma_declare_coherent_memory on main memory taken from the memblock
allocator.
Is there any good reason these couldn't be switched to CMA areas?
Getting rid of these magic dma_declare_coherent_memory area would
help making the dma allocator a lot simpler.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: iommu@lists.linux-foundation.org, linux-sh@vger.kernel.org,
linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: dma_declare_coherent_memory on main memory
Date: Fri, 7 Dec 2018 16:34:32 +0100 [thread overview]
Message-ID: <20181207153432.GA24917@lst.de> (raw)
Hi all,
the ARM imx27/31 ports and various sh boards use
dma_declare_coherent_memory on main memory taken from the memblock
allocator.
Is there any good reason these couldn't be switched to CMA areas?
Getting rid of these magic dma_declare_coherent_memory area would
help making the dma allocator a lot simpler.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-07 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 15:34 Christoph Hellwig [this message]
2018-12-07 15:34 ` dma_declare_coherent_memory on main memory Christoph Hellwig
2018-12-07 15:34 ` Christoph Hellwig
[not found] ` <20181207153432.GA24917-jcswGhMUV9g@public.gmane.org>
2018-12-08 21:25 ` Rob Landley
2018-12-08 21:25 ` Rob Landley
2018-12-08 21:25 ` Rob Landley
2018-12-08 21:25 ` Rob Landley
2018-12-10 7:26 ` Sascha Hauer
2018-12-10 7:26 ` Sascha Hauer
2018-12-10 7:26 ` Sascha Hauer
2018-12-10 19:02 ` Christoph Hellwig
2018-12-10 19:02 ` Christoph Hellwig
2018-12-10 19:02 ` 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=20181207153432.GA24917@lst.de \
--to=hch@lst.de \
--cc=fabio.estevam@nxp.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 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.