public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Ruslan Bilovol <ruslan.bilovol@ti.com>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org, balbi@ti.com
Subject: Re: [PATCH RESEND] usb: otg: OMAP4: Fix the omap4430_phy_set_clk function
Date: Mon, 2 Jul 2012 11:13:59 +0300	[thread overview]
Message-ID: <20120702081358.GF16670@arwen.pp.htv.fi> (raw)
In-Reply-To: <1339522581-8124-1-git-send-email-ruslan.bilovol@ti.com>

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

Hi,

On Tue, Jun 12, 2012 at 08:36:21PM +0300, Ruslan Bilovol wrote:
> If the clocks are enabled and we want to enable them again
> omap4430_phy_set_clk disables them.
> 
> Fix this - so now if we try to enable already enabled clocks
> it works correctly.
> 
> Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>
> ---
>  arch/arm/mach-omap2/omap_phy_internal.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-omap2/omap_phy_internal.c b/arch/arm/mach-omap2/omap_phy_internal.c
> index 4c90477..0196683 100644
> --- a/arch/arm/mach-omap2/omap_phy_internal.c
> +++ b/arch/arm/mach-omap2/omap_phy_internal.c
> @@ -97,7 +97,7 @@ int omap4430_phy_set_clk(struct device *dev, int on)
>  		clk_enable(clk48m);
>  		clk_enable(clk32k);
>  		state = 1;
> -	} else if (state) {
> +	} else if (!on && state) {

why don't you let clocks be enabled twice then ? That would cut down the
churn.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-07-02  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 17:36 [PATCH RESEND] usb: otg: OMAP4: Fix the omap4430_phy_set_clk function Ruslan Bilovol
     [not found] ` <1339522581-8124-1-git-send-email-ruslan.bilovol-l0cyMroinI0@public.gmane.org>
2012-06-20 13:31   ` Tony Lindgren
2012-06-29 21:50     ` Ruslan Bilovol
2012-07-02  8:08       ` Tony Lindgren
2012-07-02  8:13 ` Felipe Balbi [this message]
2012-07-02 17:10   ` Ruslan Bilovol
     [not found]     ` <CAEa47NokHNwkpoM-7q1BoxsNw7Cfr+qd7YsvJ2VKriHEU-A+og-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-03 16:13       ` Felipe Balbi
     [not found]         ` <20120703161349.GA23380-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-07-05 17:16           ` Ruslan Bilovol
2012-07-23 10:36             ` Felipe Balbi

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=20120702081358.GF16670@arwen.pp.htv.fi \
    --to=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ruslan.bilovol@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