From: Michal Nazarewicz <mina86@mina86.com>
To: Feng Tang <feng.tang@intel.com>
Cc: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"m.szyprowski\@samsung.com" <m.szyprowski@samsung.com>,
"kyungmin.park\@samsung.com" <kyungmin.park@samsung.com>,
"akpm\@linux-foundation.org" <akpm@linux-foundation.org>,
"iamjoonsoo.kim\@lge.com" <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH] CMA: Don't return a valid cma for non-cma dev
Date: Fri, 31 Jul 2015 19:46:30 +0200 [thread overview]
Message-ID: <xa1toaisrzih.fsf@mina86.com> (raw)
In-Reply-To: <20150731151816.GA18347@shbuild888>
On Fri, Jul 31 2015, Feng Tang wrote:
> Maybe I didn't make my problem clear, for our platform, we do need to
> use cma as we have camera ISP which has no IOMMU, so we cannot set
> "cma=0".
Then specify a CMA region for the camera in platform initialisation code
or device trees or whatever else is the rave nowadays.
I’m assuming that you have a piece of code (or configuration of some
sort) that assigns a CMA region to the device (otherwise ‘dev->cma_area’
would be NULL and your patch would just always get you NULL CMA area).
Simply create a CMA area there and assign it to the device.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--
next prev parent reply other threads:[~2015-07-31 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 2:37 [PATCH] CMA: Don't return a valid cma for non-cma dev Feng Tang
2015-07-30 13:59 ` Michal Nazarewicz
2015-07-31 2:51 ` Tang, Feng
2015-07-31 12:05 ` Michal Nazarewicz
2015-07-31 15:18 ` Feng Tang
2015-07-31 17:46 ` Michal Nazarewicz [this message]
2015-08-05 9:19 ` Feng Tang
2015-08-05 10:28 ` Michal Nazarewicz
2015-08-05 10:46 ` Feng Tang
2015-08-05 10:55 ` Feng Tang
2015-08-05 11:15 ` Michal Nazarewicz
2015-08-05 13:22 ` Feng Tang
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=xa1toaisrzih.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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.