From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Mike Turquette <mturquette@linaro.org>
Cc: Mike Turquette <mturquette@linaro.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Stephen Boyd <sboyd@codeaurora.org>,
"Alex Elder" <elder@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mips@linux-mips.org>, <linux-omap@vger.kernel.org>,
Manuel Lauss <manuel.lauss@gmail.com>,
"Matt Porter" <mporter@linaro.org>,
Ralf Baechle <ralf@linux-mips.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>
Subject: Re: [PATCH v5 0/7] Per-user clock constraints
Date: Fri, 31 Oct 2014 13:33:58 +0200 [thread overview]
Message-ID: <20141031113358.GY32045@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <1414666135-14313-1-git-send-email-tomeu.vizoso@collabora.com>
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.
next prev parent reply other threads:[~2014-10-31 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 10:48 Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 1/7] clk: Remove unused function __clk_get_prepare_count Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 2/7] clk: Don't try to use a struct clk* after it could have been freed Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 3/7] clk: Don't expose __clk_get_accuracy Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 4/7] clk: change clk_debugfs_add_file to take a struct clk_hw Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 5/7] clk: Change clk_ops->determine_rate to return a clk_hw as the best parent Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 6/7] clk: Make clk API return per-user struct clk instances Tomeu Vizoso
2014-11-14 7:06 ` Stephen Boyd
2014-11-19 14:55 ` Tomeu Vizoso
2014-10-30 10:48 ` [PATCH v5 7/7] clk: Add floor and ceiling constraints to clock rates Tomeu Vizoso
2014-11-14 7:50 ` Stephen Boyd
2014-11-18 16:31 ` Tomeu Vizoso
2014-11-22 2:35 ` Stephen Boyd
2014-11-28 13:23 ` Tomeu Vizoso
2014-10-31 11:33 ` Peter De Schrijver [this message]
2014-11-14 6:28 ` [PATCH v5 0/7] Per-user clock constraints Tomeu Vizoso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141031113358.GY32045@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=arnd@arndb.de \
--cc=elder@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=javier.martinez@collabora.co.uk \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-omap@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=mporter@linaro.org \
--cc=mturquette@linaro.org \
--cc=ralf@linux-mips.org \
--cc=sboyd@codeaurora.org \
--cc=tomeu.vizoso@collabora.com \
--cc=zhangfei.gao@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®