linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: brezillonboris@gmail.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/4] clk: at91: propagate rate change on system clks
Date: Tue, 11 Mar 2014 10:00:33 +0100	[thread overview]
Message-ID: <1394528435-23734-3-git-send-email-b.brezillon.dev@gmail.com> (raw)
In-Reply-To: <1394528435-23734-1-git-send-email-b.brezillon.dev@gmail.com>

From: Boris BREZILLON <b.brezillon@overkiz.com>

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>
---
 drivers/clk/at91/clk-system.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/clk/at91/clk-system.c b/drivers/clk/at91/clk-system.c
index 8f7c043..48c89fe 100644
--- a/drivers/clk/at91/clk-system.c
+++ b/drivers/clk/at91/clk-system.c
@@ -84,7 +84,7 @@ 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_PARENT | CLK_IGNORE_UNUSED;
 
 	sys->id = id;
 	sys->hw.init = &init;
-- 
1.7.9.5

  parent reply	other threads:[~2014-03-11  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  9:00 [PATCH v3 0/4] clk: at91: better support for the PCKs Boris BREZILLON
2014-03-11  9:00 ` [PATCH v3 1/4] clk: at91: replace prog clk round_rate with determine_rate Boris BREZILLON
2014-03-11  9:00 ` Boris BREZILLON [this message]
2014-03-11  9:00 ` [PATCH v3 3/4] clk: at91: fix programmable clk irq handling Boris BREZILLON
2014-03-11  9:00 ` [PATCH v3 4/4] clk: at91: optimization of the set_rate callback Boris BREZILLON
2014-03-19 23:32 ` [PATCH v3 0/4] clk: at91: better support for the PCKs Mike Turquette

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=1394528435-23734-3-git-send-email-b.brezillon.dev@gmail.com \
    --to=brezillonboris@gmail.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).