[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141031113358.GY32045@tbergstrom-lnx.Nvidia.com>
Date: Fri, 31 Oct 2014 13:33:58 +0200
From: Peter De Schrijver <pdeschrijver@...dia.com>
To: Tomeu Vizoso <tomeu.vizoso@...labora.com>,
Mike Turquette <mturquette@...aro.org>
CC: Mike Turquette <mturquette@...aro.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Stephen Boyd <sboyd@...eaurora.org>,
"Alex Elder" <elder@...aro.org>, Arnd Bergmann <arnd@...db.de>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
Jaehoon Chung <jh80.chung@...sung.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-mips@...ux-mips.org>, <linux-omap@...r.kernel.org>,
Manuel Lauss <manuel.lauss@...il.com>,
"Matt Porter" <mporter@...aro.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Zhangfei Gao <zhangfei.gao@...aro.org>
Subject: Re: [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@...dia.com>
Mike,
Do you think this will be merged for 3.19?
Thanks,
Peter.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists