From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Yangwei (Yang Wei,
Device Chipset Key Technologies Platform Development Dept)"
<yyangwei.yangwei@hisilicon.com>
Cc: "labbott@redhat.com" <labbott@redhat.com>,
"sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
"arve@android.com" <arve@android.com>,
"riandrews@android.com" <riandrews@android.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zengtao (B)" <prime.zeng@hisilicon.com>,
"Chenhao (benjamin)" <benjamin.chenhao@hisilicon.com>
Subject: Re: Cma mem map to cpu address when allocated in ion driver, why do this design?
Date: Thu, 1 Sep 2016 16:45:30 +0200 [thread overview]
Message-ID: <20160901144530.GC11190@kroah.com> (raw)
In-Reply-To: <ED4B3388B2AD1941A5C115675359165C3C2AE79B@SZXEMA501-MBX.china.huawei.com>
On Thu, Sep 01, 2016 at 12:46:32PM +0000, Yangwei (Yang Wei, Device Chipset Key Technologies Platform Development Dept) wrote:
> Hi all,
>
> When I review ion code in linux-3.18.y, I find a design that may cause
> a problem in our product. In the design, cma mem is allocated via the
> interface of dma_alloc_coherent ,
3.18 is old and obsolete and isn't supported by the kernel community for
anything except bug fixes. I suggest you work with whatever group is
forcing you to use this old kernel version as they are the ones that you
are paying to support this kernel for you.
If you wish to discuss the 4.7 or newer kernel versions, and how ion
works there (look in linux-next for the most recent changes in that
area), we would be glad to help you out.
Best of luck!
greg k-h
next prev parent reply other threads:[~2016-09-01 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 12:46 Cma mem map to cpu address when allocated in ion driver, why do this design? Yangwei (Yang Wei, Device Chipset Key Technologies Platform Development Dept)
2016-09-01 14:45 ` gregkh [this message]
2016-09-01 15:16 ` Laura Abbott
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=20160901144530.GC11190@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=benjamin.chenhao@hisilicon.com \
--cc=devel@driverdev.osuosl.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=riandrews@android.com \
--cc=sumit.semwal@linaro.org \
--cc=yyangwei.yangwei@hisilicon.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