linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/8] clk: Change clk_ops->determine_rate to return a clk_hw as the best parent
Date: Wed, 08 Oct 2014 18:30:21 -0700	[thread overview]
Message-ID: <5435E52D.1030806@codeaurora.org> (raw)
In-Reply-To: <1412695334-2608-7-git-send-email-tomeu.vizoso@collabora.com>

On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
> This is in preparation for clock providers to not have to deal with struct clk.
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> ---
>   drivers/clk/at91/clk-programmable.c |  4 ++--
>   drivers/clk/bcm/clk-kona.c          |  4 ++--
>   drivers/clk/clk-composite.c         |  9 +++++----
>   drivers/clk/clk.c                   | 11 +++++++----
>   drivers/clk/hisilicon/clk-hi3620.c  |  2 +-
>   drivers/clk/qcom/clk-rcg.c          | 20 ++++++++++++--------
>   drivers/clk/qcom/clk-rcg2.c         | 28 +++++++++++++++++-----------
>   drivers/clk/sunxi/clk-factors.c     |  4 ++--
>   drivers/clk/sunxi/clk-sun6i-ar100.c |  4 ++--
>   include/linux/clk-provider.h        |  4 ++--
>   10 files changed, 52 insertions(+), 38 deletions(-)

What is this based on? I see one in arch/mips/alchemy/common/clock.c as 
well.

Can you also update Documentation/clk.txt please?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2014-10-09  1:30 UTC|newest]

Thread overview: 6+ 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 ` [PATCH v2 6/8] clk: Change clk_ops->determine_rate to return a clk_hw as the best parent Tomeu Vizoso
2014-10-09  1:30   ` Stephen Boyd [this message]
2014-10-07 15:21 ` [PATCH v2 7/8] clk: Make clk API return per-user struct clk instances Tomeu Vizoso
2014-10-09  1:32 ` [PATCH v2 0/8] Per-user clock constraints Stephen Boyd
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=5435E52D.1030806@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).