[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101005075551.GJ11737@pengutronix.de>
Date: Tue, 5 Oct 2010 09:55:51 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Dinh.Nguyen@...escale.com
Cc: linux-kernel@...r.kernel.org, amit.kucheria@...onical.com,
s.hauer@...gutronix.de, grant.likely@...retlab.ca,
valentin.longchamp@...l.ch, daniel@...aq.de,
xiao-lizhang@...escale.com, r.schwebel@...gutronix.de,
linux-arm-kernel@...ts.infradead.org, kernel@...gutronix.de
Subject: Re: [PATCH] ARM: imx: Add iram allocator functions
On Tue, Oct 05, 2010 at 09:44:23AM +0200, Uwe Kleine-König wrote:
> On Mon, Oct 04, 2010 at 07:03:27PM -0500, Dinh.Nguyen@...escale.com wrote:
> > From: Dinh Nguyen <Dinh.Nguyen@...escale.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.
> >
> > Applies on 2.6.36-rc6
> >
> > Signed-off-by: Dinh Nguyen <Dinh.Nguyen@...escale.com>
> > Reviewed-by: Amit Kucheria <amit.kucheria@...onical.com>
> > ---
> > arch/arm/plat-mxc/Kconfig | 10 ++++
> > arch/arm/plat-mxc/Makefile | 1 +
> > arch/arm/plat-mxc/include/mach/iram_alloc.h | 35 +++++++++++++++
> > arch/arm/plat-mxc/iram.c | 62 +++++++++++++++++++++++++++
> > 4 files changed, 108 insertions(+), 0 deletions(-)
> > create mode 100644 arch/arm/plat-mxc/include/mach/iram_alloc.h
> > create mode 100644 arch/arm/plat-mxc/iram.c
> >
> > diff --git a/arch/arm/plat-mxc/Kconfig b/arch/arm/plat-mxc/Kconfig
> > index 6785db4..5e4ff93 100644
> > --- a/arch/arm/plat-mxc/Kconfig
> > +++ b/arch/arm/plat-mxc/Kconfig
> > @@ -57,6 +57,16 @@ source "arch/arm/mach-mx5/Kconfig"
> >
> > endmenu
> >
> > +config IRAM_ALLOC
> > + bool "Enable IRAM allocator"
> > + default y
> The iram allocator isn't useful taken alone, no? So I suggest to make
> it
Hmm. It seems I forgot to finish this sentence, sorry.
Unless IRAM_ALLOC is an optional feature for new features to come I'd
not make it user selectible, but let the new features select IRAM_ALLOC.
If it's optional I wonder if "default y" should really be done.
Maybe better call the symbol just IRAM?
> > + iram_pool = gen_pool_create(12, -1);
> if (!iram_pool)
> ...
After rereading the commit log I wondered where the 4 KB are enforced.
Maybe do
s/12/PAGE_SHIFT/
to make it more obvious?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists