lkml.org 
[lkml]   [2014]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v5 0/7] Per-user clock constraints
    On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote:
    > Hello,
    >
    > this fifth version of the series has just one change, suggested by Stephen:
    >
    > * Initialize clk.ceiling_constraint to ULONG_MAX and warn about new floor
    > constraints being higher than the existing ceiling.
    >
    > The first five patches are just cleanups that should be desirable on their own,
    > and that should make easier to review the actual per-user clock patch.
    >
    > The sixth patch actually moves the per-clock data that was stored in struct
    > clk to a new struct clk_core and adds references to it from both struct clk and
    > struct clk_hw. struct clk is now ready to contain information that is specific
    > to a given clk consumer.
    >
    > The seventh patch adds API for setting floor and ceiling constraints and stores
    > that information on the per-user struct clk, which is iterable from struct
    > clk_core.
    >
    > They are based on top of 3.18-rc1.
    >
    > http://cgit.collabora.com/git/user/tomeu/linux.git/log/?h=per-user-clk-constraints-v5
    >

    Acked-By: Peter De Schrijver <pdeschrijver@nvidia.com>

    Mike,

    Do you think this will be merged for 3.19?

    Thanks,

    Peter.


    \
     
     \ /
      Last update: 2014-10-31 13:21    [W:2.197 / U:0.736 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site