linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: CMA on arm from zero address
Date: Fri, 10 Feb 2012 11:15:56 +0100	[thread overview]
Message-ID: <4F34EE5C.7040103@monstr.eu> (raw)
In-Reply-To: <20120208132622.GL889@n2100.arm.linux.org.uk>

Russell King - ARM Linux wrote:
> On Wed, Feb 08, 2012 at 02:21:26PM +0100, Michal Simek wrote:
>> First of all I have found how to do it (by CONFIG_PHYS_OFFSET) so the
>> problem is in QEMU.
> 
> So you're basically not telling the kernel about the first 32MB of memory.

It is not a problem.

> 
>> Currently experimenting how to convince CMA to allocate that memory for
>> my purpose.
> 
> Which means it won't be part of the kernels normal memory map, and so
> won't be in the page pool.  So CMA won't be able to help.
> 
> Instead, just ignore the first 32MB of RAM, and map it like any other
> peripheral to gain access to it.  You might need to use ioremap_wc()
> to avoid treating the memory as a 'device type' in ARMv6+.

I switched from cma to dma_declare_coherent_memory which does exactly what I wanted to
do.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2012-02-10 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 12:27 CMA on arm from zero address Michal Simek
2012-02-08 13:08 ` Russell King - ARM Linux
2012-02-08 13:21   ` Michal Simek
2012-02-08 13:26     ` Russell King - ARM Linux
2012-02-10 10:15       ` Michal Simek [this message]
2012-02-08 13:30     ` Marek Szyprowski

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=4F34EE5C.7040103@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=ohad@wizery.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;
as well as URLs for NNTP newsgroup(s).