All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Michael Turquette <mturquette@baylibre.com>,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] clk: pxa: export core clocks
Date: Tue, 1 Nov 2016 17:56:51 -0700	[thread overview]
Message-ID: <20161102005651.GZ16026@codeaurora.org> (raw)
In-Reply-To: <1477225170-19019-5-git-send-email-robert.jarzmik@free.fr>

On 10/23, Robert Jarzmik wrote:
> pxaxxx_get_clk_frequency_khz() needs several clocks to be available
> through clk_get(), ie. the cpu clocks, system bus clock and memory
> clocks.
> 
> Add the missing clkdev so that their rate can be acquired.
> 
> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> ---

Applied to clk-next

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

  reply	other threads:[~2016-11-02  0:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-23 12:19 [PATCH v2 0/5] Make pxa core clocks settable Robert Jarzmik
2016-10-23 12:19 ` [PATCH v2 1/5] clk: pxa: remove unused variables Robert Jarzmik
2016-11-02  0:56   ` Stephen Boyd
2016-10-23 12:19 ` [PATCH v2 2/5] clk: pxa: core pll is not affected by t bit Robert Jarzmik
2016-11-02  0:56   ` Stephen Boyd
2016-10-23 12:19 ` [PATCH v2 3/5] clk: pxa: b bit of clkcfg means fast bus Robert Jarzmik
2016-11-02  0:56   ` Stephen Boyd
2016-10-23 12:19 ` [PATCH v2 4/5] clk: pxa: export core clocks Robert Jarzmik
2016-11-02  0:56   ` Stephen Boyd [this message]
2016-10-23 12:19 ` [PATCH v2 5/5] clk: pxa: transfer CPU clock setting from pxa2xx-cpufreq Robert Jarzmik
2016-11-02  0:56   ` Stephen Boyd
2016-11-02 15:49     ` Robert Jarzmik
2016-11-02 22:26       ` Stephen Boyd

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=20161102005651.GZ16026@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robert.jarzmik@free.fr \
    /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.