[PATCH v5 0/7] Per-user clock constraints
tomeu.vizoso at collabora.com
Thu Nov 13 22:28:12 PST 2014
On 31 October 2014 12:33, Peter De Schrijver <pdeschrijver at nvidia.com> wrote:
> On Thu, Oct 30, 2014 at 11:48:26AM +0100, Tomeu Vizoso wrote:
>> this fifth version of the series has just one change, suggested by Stephen:
Hi Mike, how is this looking for 3.19?
>> * 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
>> They are based on top of 3.18-rc1.
> Acked-By: Peter De Schrijver <pdeschrijver at nvidia.com>
> Do you think this will be merged for 3.19?
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
More information about the linux-arm-kernel