From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/1] ARM: imx: clk-pllv3: change wait method for PLL lock
Date: Sun, 14 Jul 2013 08:43:04 +0800 [thread overview]
Message-ID: <20130714004303.GA15443@nchen-desktop> (raw)
In-Reply-To: <20130608010922.GA25105@nchen-desktop>
On Sat, Jun 08, 2013 at 09:09:23AM +0800, Peter Chen wrote:
> On Fri, Jun 07, 2013 at 07:07:43PM +0800, Shawn Guo wrote:
> > On Fri, Jun 07, 2013 at 10:49:38AM +0200, Uwe Kleine-K?nig wrote:
> > > > I will try your fix, but still it just reduces the possibilities.
> > > > The problem is not the preemption takes too long, it is the jiffies
> > > > updates more than one tick at one short preemption.
> > > If that is really the problem that many more instances that use the same
> > > incarnation need the same fix. I would be surprised if that was the
> > > case.
> >
> > +1
> >
>
> Using uwe's patch, the pll lock timeout hasn't appeared during the
> overtime test, usually, it will occur 4 or 5 times during overnight
> test. The reason why I suspect jiffies update problem that is we
> meet the similiar issue at other drivers which timeout is 2 jiffies,
> but it is satisfied within 1ms.
>
> I will do more test, if it is passed, I will send patch with uwe's suggestion.
> Thanks.
The root cause of this problem is timer problem, Jason has already submitted a patch
to fix this problem.
http://marc.info/?l=linux-arm-kernel&m=137109340222931&w=2
I will send a improvement patch with uwe's suggestion.
--
Best Regards,
Peter Chen
prev parent reply other threads:[~2013-07-14 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 8:19 [PATCH v2 1/1] ARM: imx: clk-pllv3: change wait method for PLL lock Peter Chen
2013-06-07 8:24 ` Uwe Kleine-König
2013-06-07 8:31 ` Peter Chen
2013-06-07 8:35 ` Uwe Kleine-König
2013-06-07 8:43 ` Peter Chen
2013-06-07 8:49 ` Uwe Kleine-König
2013-06-07 11:07 ` Shawn Guo
2013-06-08 1:09 ` Peter Chen
2013-07-14 0:43 ` Peter Chen [this message]
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=20130714004303.GA15443@nchen-desktop \
--to=peter.chen@freescale.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 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.