RE: Question on OPP table handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Typo I meant Put all the OPP tables for different CPUs (instead ofOPPs) in __initdata. Copy the run time detected CPU's OPP table in memory. Others get discarded!"

>-----Original Message-----
>From: Menon, Nishanth
>Sent: Tuesday, October 06, 2009 5:34 PM
>To: Dasgupta, Romit
>Cc: Premi, Sanjeev; Cousson, Benoit; Kevin H; linux-omap@xxxxxxxxxxxxxxx
>Subject: Re: Question on OPP table handling
>
>Dasgupta, Romit had written, on 10/06/2009 07:00 AM, the following:
>>> Couple of opinions on why a list with disabled/invalid marker might not
>>> make sense as a grand unified OPP table:
>>> a) it is no better than a list implementation
>>> b) it is a waste of memory.
>> [Romit] Put all the OPP tables for different OPPs in __initdata. Copy the runtime
>detected CPU's OPP table in memory. Others get discarded!
>>
>I like this approach.. takers?
>
>--
>Regards,
>Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux