From: Tony Lindgren <tony@atomide.com>
To: Abhijit Pagare <abhijitpagare@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>,
Rajendra Nayak <rnayak@ti.com>
Subject: Re: [PATCH 1/1] ARM: OMAP4: PM: Remove the checks preventing OMAP4 clockdomain validation
Date: Mon, 28 Dec 2009 11:47:31 -0800 [thread overview]
Message-ID: <20091228194731.GL3512@atomide.com> (raw)
In-Reply-To: <1261391747-24066-1-git-send-email-abhijitpagare@ti.com>
* Abhijit Pagare <abhijitpagare@ti.com> [091221 02:34]:
> The clockdomain related code beng in place it is now not necessary to have
> some of the clock code commented out. This would help the validation of the
> clockdomain functions using the clock level interfaces.
Why are tagging clock related patches as "PM" in the subject?
All the clock related patches should be done directly against
the mainline kernel.
If there is some dependency to the pm branch, that should be
fixed and removed ASAP.
Regards,
Tony
> Signed-off-by: Abhijit Pagare <abhijitpagare@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> Cc: Benoit Cousson <b-cousson@ti.com>
> Cc: Rajendra Nayak <rnayak@ti.com>
> ---
> arch/arm/mach-omap2/clock.c | 8 --------
> 1 files changed, 0 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clock.c b/arch/arm/mach-omap2/clock.c
> index 759c72a..a6d570a 100644
> --- a/arch/arm/mach-omap2/clock.c
> +++ b/arch/arm/mach-omap2/clock.c
> @@ -181,7 +181,6 @@ static int _dpll_test_fint(struct clk *clk, u8 n)
> * clockdomain pointer, and save it into the struct clk. Intended to be
> * called during clk_register(). No return value.
> */
> -#ifndef CONFIG_ARCH_OMAP4 /* FIXME: Remove this once clkdm f/w is in place */
> void omap2_init_clk_clkdm(struct clk *clk)
> {
> struct clockdomain *clkdm;
> @@ -199,7 +198,6 @@ void omap2_init_clk_clkdm(struct clk *clk)
> "clkdm %s\n", clk->name, clk->clkdm_name);
> }
> }
> -#endif
>
> /**
> * omap2_init_clksel_parent - set a clksel clk's parent field from the hardware
> @@ -476,10 +474,8 @@ void omap2_clk_disable(struct clk *clk)
> _omap2_clk_disable(clk);
> if (clk->parent)
> omap2_clk_disable(clk->parent);
> -#ifndef CONFIG_ARCH_OMAP4 /* FIXME: Remove this once clkdm f/w is in place */
> if (clk->clkdm)
> omap2_clkdm_clk_disable(clk->clkdm, clk);
> -#endif
>
> }
> }
> @@ -489,10 +485,8 @@ int omap2_clk_enable(struct clk *clk)
> int ret = 0;
>
> if (clk->usecount++ == 0) {
> -#ifndef CONFIG_ARCH_OMAP4 /* FIXME: Remove this once clkdm f/w is in place */
> if (clk->clkdm)
> omap2_clkdm_clk_enable(clk->clkdm, clk);
> -#endif
>
> if (clk->parent) {
> ret = omap2_clk_enable(clk->parent);
> @@ -511,10 +505,8 @@ int omap2_clk_enable(struct clk *clk)
> return ret;
>
> err:
> -#ifndef CONFIG_ARCH_OMAP4 /* FIXME: Remove this once clkdm f/w is in place */
> if (clk->clkdm)
> omap2_clkdm_clk_disable(clk->clkdm, clk);
> -#endif
> clk->usecount--;
> return ret;
> }
> --
> 1.5.4.7
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-28 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 10:35 [PATCH 1/1] ARM: OMAP4: PM: Remove the checks preventing OMAP4 clockdomain validation Abhijit Pagare
2009-12-22 16:12 ` Paul Walmsley
2009-12-23 11:27 ` Pagare, Abhijit
2009-12-28 19:47 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-23 15:47 Abhijit Pagare
2009-12-30 8:34 ` Paul Walmsley
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=20091228194731.GL3512@atomide.com \
--to=tony@atomide.com \
--cc=abhijitpagare@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@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