From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Dinh.Nguyen@freescale.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, s.hauer@pengutronix.de,
r.schwebel@pengutronix.de, valentin.longchamp@epfl.ch,
daniel@caiaq.de, grant.likely@secretlab.ca,
amit.kucheria@canonical.com, xiao-lizhang@freescale.com
Subject: Re: [PATCHv3] ARM: imx: Add iram allocator functions
Date: Tue, 5 Oct 2010 21:55:51 +0200 [thread overview]
Message-ID: <AANLkTim+WNx1B860AgHeP_X2u7HRC3=40j3FKgAg_BXf@mail.gmail.com> (raw)
In-Reply-To: <1286307715-12276-1-git-send-email-Dinh.Nguyen@freescale.com>
2010/10/5 <Dinh.Nguyen@freescale.com>:
> Add iram allocation functions using GENERIC_ALLOCATOR. The
> allocation size is 4KB multiples to guarantee alignment. The
> idea for these functions is for i.MX platforms to use them
> to dynamically allocate IRAM usage.
Neither here...
> +config IRAM_ALLOC
> + bool "Enable IRAM allocator"
> + select GENERIC_ALLOCATOR
> + help
> + Select this to have access to generic IRAM allocation functions that
> + use the GENERIC_ALLOCATOR. The allocation size is 4KB multiples to
> + guarantee alignment. The idea for these functions is for i.MX platforms
> + to use them to dynamically allocate IRAM usage.
Nor here is is explained what an IRAM is.
What is it? Is this yet another fancy name for on-chip-memory?
And why I? = Initial? Interrupt? ...?
Yours,
Linus Walleij
next prev parent reply other threads:[~2010-10-05 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:41 Dinh.Nguyen
2010-10-05 19:55 ` Linus Walleij [this message]
2010-10-05 20:22 ` Uwe Kleine-König
2010-10-06 16:04 ` Nguyen Dinh-R00091
2010-10-06 10:35 ` Sascha Hauer
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='AANLkTim+WNx1B860AgHeP_X2u7HRC3=40j3FKgAg_BXf@mail.gmail.com' \
--to=linus.ml.walleij@gmail.com \
--cc=Dinh.Nguyen@freescale.com \
--cc=amit.kucheria@canonical.com \
--cc=daniel@caiaq.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=valentin.longchamp@epfl.ch \
--cc=xiao-lizhang@freescale.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
all inboxes | Powered by JetHome®