Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755315Ab2EWJUh (ORCPT ); Wed, 23 May 2012 05:20:37 -0400 Received: from hqemgate04.nvidia.com ([216.228.121.35]:6776 "EHLO hqemgate04.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750895Ab2EWJUg (ORCPT ); Wed, 23 May 2012 05:20:36 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Wed, 23 May 2012 02:19:04 -0700 Date: Wed, 23 May 2012 12:19:54 +0300 From: Peter De Schrijver To: "Turquette, Mike" CC: Ben Dooks , Prashant Gaikwad , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: Clock register in early init Message-ID: <20120523091954.GA8730@tbergstrom-lnx.Nvidia.com> References: <1337227884.2066.9.camel@pgaikwad-dt2> <20120517062131.GA9305@gmail.com> <1337316517.22560.19.camel@pgaikwad-dt2> <20120518112104.GL20304@tbergstrom-lnx.Nvidia.com> <20120521084642.GV20304@tbergstrom-lnx.Nvidia.com> <4FBB5A72.2080101@codethink.co.uk> <20120522120851.GI8730@tbergstrom-lnx.Nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1249 Lines: 31 On Tue, May 22, 2012 at 07:37:15PM +0200, Turquette, Mike wrote: > On Tue, May 22, 2012 at 5:08 AM, Peter De Schrijver > wrote: > >> We had at-least that on the older Samsung parts and they where still > >> growing. I would suggest that in a multi-kernel image situation the > >> more data that can be discarded after init-time the better. > >> > >> Also, __initdata gets gathered into one place so there's no possibility > >> of page fragmentation there. If you mean fragmentation of the memory > >> map, then allocate the size of all the clocks you know of at init time > >> in one go. > >> > > > > That would work, except that clocks are needed before kmalloc is available. > > > > Is static initialization the only way to solve this problem? What > about using the bootmem allocator for early init clocks? > If it can be handled inside the framework somehow. I would want to avoid having several places where clocks inside the same SoC are initialized. Cheers, Peter. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/