[lkml]   [2012]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] clk: Constify struct clk_init_data
    On Mon, May 14, 2012 at 10:13 PM, Rajendra Nayak <> wrote:
    > Hi Saravana,
    > On Tuesday 15 May 2012 06:38 AM, Saravana Kannan wrote:
    >> Btw, I didn't follow up on the other thread we were having, but can you
    >> remind me again what was the reason that you thought that only
    >> __clk_init() would work for your static init code and __clk_register()
    >> won't work?
    > One of the main reason has been the platform implementation we have to
    > handle some complex mux/divider combo clocks in OMAP2/3 which rely on
    > 'struct clk' pointers. Maybe we can do away with the existing
    > implementation and redo it so we don't have any such limitation, but the
    > quantum of change moving to common clk has been so much that we are
    > trying to minimize on the platform code changes for now. So while
    > we move to common clk it would still be useful to have __clk_init()
    > around for a while till we figure out how to get rid of it for OMAP.

    Just to add to what Rajendra has stated for OMAP: after OMAP's
    conversion is finally made initcall-able then I'll get rid of lots of
    the gross macros and before-the-memory-allocator-is-alive stuff. I'll
    make sure that no other platforms are using those bits of course, but
    I plan on removing some of this stuff from the core once my platform
    is up to speed.


    > regards,
    > Rajendra

     \ /
      Last update: 2012-05-15 09:01    [W:0.024 / U:8.984 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site