From: Stephen Boyd <sboyd@codeaurora.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
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-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>,
Tim Kryger <tim.kryger@linaro.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>
Subject: Re: [PATCH v2 0/8] Per-user clock constraints
Date: Wed, 08 Oct 2014 18:32:32 -0700 [thread overview]
Message-ID: <5435E5B0.90900@codeaurora.org> (raw)
In-Reply-To: <1412695334-2608-1-git-send-email-tomeu.vizoso@collabora.com>
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
> Hello,
>
> this second version of the series adds several cleanups that were suggested by
> Stephen Boyd and contains several improvements to the seventh patch (clk: Make
> clk API return per-user struct clk instances) that were suggested by him during
> the review of v1.
>
> The first six 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 seventh 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 eighth 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.
>
>
As said in the patches, can you please indicate which baseline this is
on? Also can you rebase onto clk-next if you send again before that is
merged into 3.18-rc1? There are some changes in the debugfs part that
will conflict. I'll review the more complicated parts in detail soon.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] Per-user clock constraints
Date: Wed, 08 Oct 2014 18:32:32 -0700 [thread overview]
Message-ID: <5435E5B0.90900@codeaurora.org> (raw)
In-Reply-To: <1412695334-2608-1-git-send-email-tomeu.vizoso@collabora.com>
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
> Hello,
>
> this second version of the series adds several cleanups that were suggested by
> Stephen Boyd and contains several improvements to the seventh patch (clk: Make
> clk API return per-user struct clk instances) that were suggested by him during
> the review of v1.
>
> The first six 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 seventh 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 eighth 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.
>
>
As said in the patches, can you please indicate which baseline this is
on? Also can you rebase onto clk-next if you send again before that is
merged into 3.18-rc1? There are some changes in the debugfs part that
will conflict. I'll review the more complicated parts in detail soon.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-09 1:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:21 [PATCH v2 0/8] Per-user clock constraints Tomeu Vizoso
2014-10-07 15:21 ` Tomeu Vizoso
2014-10-07 15:21 ` [PATCH v2 1/8] MIPS: Alchemy: Remove direct access to prepare_count field of struct clk Tomeu Vizoso
2014-10-07 15:21 ` [PATCH v2 2/8] clk: Remove unused function __clk_get_prepare_count Tomeu Vizoso
2014-10-09 1:25 ` Stephen Boyd
2014-10-07 15:21 ` [PATCH v2 3/8] clk: Don't try to use a struct clk* after it could have been freed Tomeu Vizoso
2014-10-07 15:21 ` [PATCH v2 4/8] clk: Don't expose __clk_get_accuracy Tomeu Vizoso
2014-10-09 1:26 ` Stephen Boyd
2014-10-07 15:21 ` [PATCH v2 5/8] clk: change clk_debugfs_add_file to take a struct clk_hw Tomeu Vizoso
2014-10-09 1:26 ` Stephen Boyd
2014-10-07 15:21 ` [PATCH v2 6/8] clk: Change clk_ops->determine_rate to return a clk_hw as the best parent Tomeu Vizoso
2014-10-07 15:21 ` Tomeu Vizoso
2014-10-09 1:30 ` Stephen Boyd
2014-10-09 1:30 ` Stephen Boyd
2014-10-07 15:21 ` [PATCH v2 7/8] clk: Make clk API return per-user struct clk instances Tomeu Vizoso
2014-10-07 15:21 ` Tomeu Vizoso
2014-10-07 15:21 ` [PATCH v2 8/8] clk: Add floor and ceiling constraints to clock rates Tomeu Vizoso
2014-10-09 1:32 ` Stephen Boyd [this message]
2014-10-09 1:32 ` [PATCH v2 0/8] Per-user clock constraints Stephen Boyd
2014-10-09 7:21 ` Tomeu Vizoso
2014-10-09 7:21 ` 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=5435E5B0.90900@codeaurora.org \
--to=sboyd@codeaurora.org \
--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-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=tim.kryger@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.