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>,
"john.stultz\@linaro.org" <john.stultz@linaro.org>
Subject: Re: [PATCH] CMA: Don't return a valid cma for non-cma dev
Date: Wed, 05 Aug 2015 13:15:50 +0200 [thread overview]
Message-ID: <xa1tio8uc7fd.fsf@mina86.com> (raw)
In-Reply-To: <20150805105558.GA8875@shbuild888>
> On Wed, Aug 05, 2015 at 12:28:03PM +0200, Michal Nazarewicz wrote:
>> If you need several CMA areas to allocate from, create multiple struct
>> devices.
On Wed, Aug 05 2015, Feng Tang wrote:
> I've made a quick patch, which works ok on our multiple cma heap cases.
> ---
> diff --git a/drivers/staging/android/ion/ion_cma_heap.c b/drivers/staging/android/ion/ion_cma_heap.c
> index f4211f1..ee9c5d1 100644
> --- a/drivers/staging/android/ion/ion_cma_heap.c
> +++ b/drivers/staging/android/ion/ion_cma_heap.c
> @@ -29,6 +29,7 @@
> struct ion_cma_heap {
> struct ion_heap heap;
> struct device *dev;
> + struct device default_dma_dev;
I’m unfamiliar with ION code so cannot comment in great detail, butwhy
do you need dev and default_dma_dev fields? Just make dev a non-pointer
and use that.
> };
>
> #define to_cma_heap(x) container_of(x, struct ion_cma_heap, heap)
> @@ -180,9 +181,14 @@ struct ion_heap *ion_cma_heap_create(struct ion_platform_heap *data)
> return ERR_PTR(-ENOMEM);
>
> cma_heap->heap.ops = &ion_cma_ops;
> - /* get device from private heaps data, later it will be
> - * used to make the link with reserved CMA memory */
> - cma_heap->dev = data->priv;
> +
> + cma_heap->dev = &cma_heap->default_dma_dev;
> + cma_heap->dev->coherent_dma_mask = DMA_BIT_MASK(32);
> + cma_heap->dev->dma_mask = &dev->coherent_dma_mask;
> +
> + /* data->priv contains a pointer to struct cma */
> + dev_set_cma_area(cma_heap->dev, data->priv);
In the previous code, data->priv seemed to be struct device*, but in
this code it is used as struct cma*.
> +
> cma_heap->heap.type = ION_HEAP_TYPE_DMA;
> return &cma_heap->heap;
> }
But yeah, in general, from CMA’s point of view, this looks good.
--
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-08-05 11:15 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
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 [this message]
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=xa1tio8uc7fd.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.stultz@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox