Clock register in early init

[Turquette, Mike]

On Wed, May 23, 2012 at 2:19 AM, Peter De Schrijver
<pdeschrijver at nvidia.com> wrote:
> 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
>> <pdeschrijver at nvidia.com> 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.
>

I'll look into the bootmem thing.  Paul mentioned that a long time
ago.  Hopefully it can be done in such a way as to expose the same
interfaces as the dynamic allocation routines.  I'll keep you Cc'd.

Regards,
Mike

> Cheers,
>
> Peter.