linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [Query] how to handle must be always enabled clk but there's no driver use the clk
Date: Fri, 29 May 2015 19:40:11 +0800	[thread overview]
Message-ID: <20150529194011.033fa675@xhacker> (raw)

Hi Sebastian, Mike and all,

Let me describe the situation:

there's one clk called as perifsysclk, it's the system AXI clk and at the same
time it's the clock source of two gate clks, for example ethclk, sdioclk etc.
Once cold boot, HW enables perifsysclk by default,

Now let's assume eth driver is firstly probed, in the beginning of eth_probe()
we call clk_prepare_enable(ethclk);

but the eth_probe() fail due to something, so in its failed path, it calls

clk_disable_unprepare(ethclk);

which will finally disable the perifsysclk, so we hang here.


How to handle this situation? Register one dummy driver early then
clk_prepare_enable(perifsysclk) in the driver probe?

Thanks,
Jisheng

                 reply	other threads:[~2015-05-29 11:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150529194011.033fa675@xhacker \
    --to=jszhang@marvell.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).