From: Tony Lindgren <tony@atomide.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 01:08:26 -0700 [thread overview]
Message-ID: <20120702080825.GC1122@atomide.com> (raw)
In-Reply-To: <CAEa47NrLyKS-HDgruoSWAh-ZT_jtZs3Bd3C8xNtiqfOH3DejLQ@mail.gmail.com>
* Ruslan Bilovol <ruslan.bilovol@ti.com> [120629 14:55]:
> On Wed, Jun 20, 2012 at 4:31 PM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Ruslan Bilovol <ruslan.bilovol@ti.com> [120612 10:42]:
> > > 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.
> >
> > Sounds like Felipe is on vacation. Trying to figure out if this
> > is something for the fixes branch:
> >
> > What happens if this not fixed, do you get some error?
>
> The function is designed for simple clocks on-off:
> if zero "on" parameter is passed - switch the clocks off,
> if non-zero "on" parameter passed - switch the clocks on.
>
> But due to error in implementation, it works wrong if called twice or more
> times with non-zero "on" parameter.
>
> For example, assuming that clocks are disabled:
> omap4430_phy_set_clk(dev, 1); <=== enables clocks
> omap4430_phy_set_clk(dev, 1); <=== suddenly disables clocks,
> when we expect enabling.
> omap4430_phy_set_clk(dev, 1); <=== enables clocks again
>
> It seems impact of this wrong behavior is not observed on current code
> base, but we see
> crashes caused by access to non-clocked registers when heavy use this function
> in the charger detection or after implementing otg EYE improvement.
Yes thanks for explaining. Can you please update the commit message a bit
with the explanation above?
> > Was this caused by some recent commit?
>
> No, we have this wrong behavior since the omap_phy_internal.c file
> creation (c33fad0c37)
OK. It's probably safest to wait for Felipe to take a look at this
patch then and queue it for v3.6 -rc cycle.
Regards,
Tony
> > > 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) {
> > > /* Disable the phy clocks */
> > > clk_disable(phyclk);
> > > clk_disable(clk48m);
> > > --
> > > 1.7.1
--
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:[~2012-07-02 8:08 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 [this message]
2012-07-02 8:13 ` Felipe Balbi
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=20120702080825.GC1122@atomide.com \
--to=tony@atomide.com \
--cc=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 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.