From: Lucas Stach <l.stach@pengutronix.de>
To: "Andrew Morton" <akpm@linux-foundation.org>,
"Yue Hu" <huyue2@yulong.com>,
"Michał Nazarewicz" <mina86@mina86.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Dmitry Vyukov" <dvyukov@google.com>
Cc: etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: [PATCH 1/2] mm: cma: export functions to get CMA base and size
Date: Wed, 29 May 2019 12:43:11 +0200 [thread overview]
Message-ID: <20190529104312.27835-1-l.stach@pengutronix.de> (raw)
Make them usable in modules. Some drivers want to know where their
device CMA area is located to make better decisions about the DMA
programming.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
mm/cma.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/cma.c b/mm/cma.c
index 3340ef34c154..191c89bf038d 100644
--- a/mm/cma.c
+++ b/mm/cma.c
@@ -44,11 +44,13 @@ phys_addr_t cma_get_base(const struct cma *cma)
{
return PFN_PHYS(cma->base_pfn);
}
+EXPORT_SYMBOL_GPL(cma_get_base);
unsigned long cma_get_size(const struct cma *cma)
{
return cma->count << PAGE_SHIFT;
}
+EXPORT_SYMBOL_GPL(cma_get_size);
const char *cma_get_name(const struct cma *cma)
{
--
2.20.1
next reply other threads:[~2019-05-29 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 10:43 Lucas Stach [this message]
2019-05-29 10:43 ` [PATCH 2/2] drm/etnaviv: use CMA area to compute linear window offset if possible Lucas Stach
2021-05-03 7:46 ` Primoz Fiser
2019-05-30 6:26 ` [PATCH 1/2] mm: cma: export functions to get CMA base and size 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=20190529104312.27835-1-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=etnaviv@lists.freedesktop.org \
--cc=huyue2@yulong.com \
--cc=kernel@pengutronix.de \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mina86@mina86.com \
--cc=patchwork-lst@pengutronix.de \
/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