From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] clk: at91: propagate rate change on system clks
Date: Tue, 4 Feb 2014 10:05:08 +0100 [thread overview]
Message-ID: <52F0AD44.6090203@atmel.com> (raw)
In-Reply-To: <1391426731-9392-4-git-send-email-b.brezillon@overkiz.com>
On 03/02/2014 12:25, Boris BREZILLON :
> System clks are just gates, and thus do not provide any rate operations.
> Authorize clk rate change to be propagated to system clk parents.
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> drivers/clk/at91/clk-system.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/at91/clk-system.c b/drivers/clk/at91/clk-system.c
> index 8f7c043..a98557b 100644
> --- a/drivers/clk/at91/clk-system.c
> +++ b/drivers/clk/at91/clk-system.c
> @@ -84,7 +84,8 @@ at91_clk_register_system(struct at91_pmc *pmc, const char *name,
> * (see drivers/memory) which would request and enable the ddrck clock.
> * When this is done we will be able to remove CLK_IGNORE_UNUSED flag.
> */
> - init.flags = CLK_IGNORE_UNUSED;
> + init.flags = CLK_SET_RATE_GATE | CLK_SET_RATE_PARENT |
> + CLK_IGNORE_UNUSED;
>
> sys->id = id;
> sys->hw.init = &init;
>
--
Nicolas Ferre
next prev parent reply other threads:[~2014-02-04 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 11:25 [PATCH 0/3] clk: at91: various fixes and improvements Boris BREZILLON
2014-02-03 11:25 ` [PATCH 1/3] clk: at91: fix programmable clk irq handling Boris BREZILLON
2014-02-04 9:04 ` Nicolas Ferre
2014-02-03 11:25 ` [PATCH 2/3] clk: at91: replace prog clk round_rate with determine_rate Boris BREZILLON
2014-02-04 9:04 ` Nicolas Ferre
2014-02-03 11:25 ` [PATCH 3/3] clk: at91: propagate rate change on system clks Boris BREZILLON
2014-02-04 9:05 ` Nicolas Ferre [this message]
2014-02-04 13:51 ` [PATCH 0/3] clk: at91: various fixes and improvements Boris BREZILLON
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=52F0AD44.6090203@atmel.com \
--to=nicolas.ferre@atmel.com \
--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).