• N
    cpufreq: OMAP: fix freq_table leak · 1c78217f
    Nishanth Menon 提交于
    We use a single frequency table for multiple CPUs. But, with
    OMAP4, since we have multiple CPUs, the cpu_init call for CPU1
    causes freq_table previously allocated for CPU0 to be overwritten.
    In addition, we dont free the table on exit path.
    
    We solve this by maintaining an atomic type counter to ensure
    just a single table exists at a given time.
    Signed-off-by: NNishanth Menon <nm@ti.com>
    Signed-off-by: NKevin Hilman <khilman@ti.com>
    1c78217f
omap-cpufreq.c 6.4 KB