From: Todd Poynor <toddpoynor@google.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: paul@pwsan.com, rnayak@ti.com, santosh.shilimkar@ti.com,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v2 6/7] OMAP2+: clockdomain: Add 2 APIs to control clockdomain from hwmod framework
Date: Sun, 26 Jun 2011 13:07:15 -0700 [thread overview]
Message-ID: <20110626200715.GB2306@google.com> (raw)
In-Reply-To: <1308917193-16912-7-git-send-email-b-cousson@ti.com>
On Fri, Jun 24, 2011 at 02:06:32PM +0200, Benoit Cousson wrote:
> Duplicate the existing API for clockdomain enable from clock to enable
> a clock domain from hwmod framework.
> This will be needed when the hwmod framework will move from the current
> clock centric approach to the module based approach.
>
...
> +static int _clkdm_clk_hwmod_disable(struct clockdomain *clkdm)
> +{
> + if (!clkdm || !arch_clkdm || !arch_clkdm->clkdm_clk_disable)
> + return -EINVAL;
> +
> +#ifdef DEBUG
> + if (atomic_read(&clkdm->usecount) == 0) {
> + WARN_ON(1); /* underflow */
> + return -ERANGE;
> + }
> +#endif
> +
> + if (atomic_dec_return(&clkdm->usecount) > 0)
> + return 0;
Suggest taking the error return out of the #ifdef DEBUG code (mainly
to lessen the chance that enabling debugging features makes problems
appear or disappear, although the WARN_ON should be a prominent clue
in this case), and maybe just have the function always handle
underflow.
...
> @@ -877,35 +911,93 @@ int clkdm_clk_enable(struct clockdomain *clkdm, struct clk *clk)
> */
> int clkdm_clk_disable(struct clockdomain *clkdm, struct clk *clk)
> {
> + int ret = 0;
> +
> /*
> * XXX Rewrite this code to maintain a list of enabled
> * downstream clocks for debugging purposes?
> */
>
> - if (!clkdm || !clk)
> + if (!clk)
> return -EINVAL;
>
> - if (!arch_clkdm || !arch_clkdm->clkdm_clk_disable)
> + ret = _clkdm_clk_hwmod_disable(clkdm);
> +
> + /* All downstream clocks of this clockdomain are now disabled */
> + pr_debug("clockdomain: clkdm %s: clk %s now disabled\n", clkdm->name,
> + clk->name);
The pr_debug should be printed only if ret == 0.
The comment seems true only if the clock domain's usecount went to zero.
The terminology here may be a bit confusing: the function does not actually
disable the named downstream clock in the usual sense
(as in clk_disable(clk), or any action to individually gate that
clock) Similar comments for clkdm_clk_enable).
Similar comments for clkdm_hwmod_disable.
next prev parent reply other threads:[~2011-06-26 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 12:06 [PATCH v2 0/7] Fix module-mode enable sequence on OMAP4 Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 1/7] OMAP2+: clockdomain: Add an api to read idle mode Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 2/7] OMAP2+: clockdomain: Add SoC support for clkdm_is_idle Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 3/7] OMAP2+: PM: Initialise sleep_switch to a non-valid value Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 4/7] OMAP2+: PM: idle clkdms only if already in idle Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 5/7] OMAP4: PM: TEMP: Prevent l3init from idling/force sleep Benoit Cousson
2011-06-24 12:06 ` [PATCH v2 6/7] OMAP2+: clockdomain: Add 2 APIs to control clockdomain from hwmod framework Benoit Cousson
2011-06-26 20:07 ` Todd Poynor [this message]
2011-06-27 9:18 ` Cousson, Benoit
2011-06-24 12:06 ` [PATCH v2 7/7] OMAP2+: hwmod: Follow the recommended PRCM module enable sequence Benoit Cousson
2011-06-24 13:23 ` [PATCH v2 0/7] Fix module-mode enable sequence on OMAP4 Rajendra Nayak
2011-06-24 13:31 ` Cousson, Benoit
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=20110626200715.GB2306@google.com \
--to=toddpoynor@google.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
/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