All of lore.kernel.org
 help / color / mirror / Atom feed
From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: clock framework: Don't disable a clock already enabled by boot loader?
Date: Fri, 24 May 2013 14:44:58 +0200	[thread overview]
Message-ID: <519F60CA.6090302@de.bosch.com> (raw)

Hi,

we register a clock using clk_register_clkdev() etc already enabled by a 
boot loader. We are doing only the clk_register_clkdev(), but no 
clock_enable() etc on this clock.

With this, enable_count for this clock is zero, while in fact it's 
already on. I.e. the kernel doesn't know that it is on.

This results in

late_initcall(clk_disable_unused())

disabling this clock because the kernel thinks it's unused.

Is this the intended behavior? Is there a way to let the kernel know 
"the clock is enabled already, set enable_count != 0"? Or is the only 
way to do this correctly calling clock_enable() on an already enabled clock?

Many thanks and best regards

Dirk

             reply	other threads:[~2013-05-24 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 12:44 Dirk Behme [this message]
2013-05-24 23:00 ` clock framework: Don't disable a clock already enabled by boot loader? Sascha Hauer
2013-05-25  5:59   ` Dirk Behme
2013-05-25  6:54     ` Shawn Guo
2013-05-25  7:16       ` Dirk Behme
2013-05-25 11:17         ` Shawn Guo

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=519F60CA.6090302@de.bosch.com \
    --to=dirk.behme@de.bosch.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 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.