From: Felipe Balbi <felipe.balbi@nokia.com>
To: "Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
"Koskinen Aaro (Nokia-D/Helsinki)" <aaro.koskinen@nokia.com>
Subject: Re: [PATCH 1/3] omap: fix clocksource_32k to start from zero
Date: Wed, 7 Apr 2010 13:02:31 +0300 [thread overview]
Message-ID: <20100407100231.GY16297@nokia.com> (raw)
In-Reply-To: <1270634244-22741-1-git-send-email-felipe.balbi@nokia.com>
Hi,
On Wed, Apr 07, 2010 at 11:57:22AM +0200, Balbi Felipe (Nokia-D/Helsinki) wrote:
>From: Aaro Koskinen <aaro.koskinen@nokia.com>
>
>When the 32k sync timer is used for sched_clock(), it should count
>time from the kernel boot (clocksource init) instead of the last HW
>reset. Otherwise printk.time values will jump suddenly during the boot:
>
> [ 0.000000] calling omap2_clk_arch_init+0x0/0x138 @ 1
> [ 0.000000] initcall omap2_clk_arch_init+0x0/0x138 returned -22 after 0 usecs
> [ 0.000000] initcall omap2_clk_arch_init+0x0/0x138 returned with error code -22
> [ 0.000000] calling omap_init_clocksource_32k+0x0/0x98 @ 1
> [ 508.697937] initcall omap_init_clocksource_32k+0x0/0x98 returned 0 after 0 usecs
> [ 508.697967] calling omap_init_devices+0x0/0x38 @ 1
> [ 508.698425] initcall omap_init_devices+0x0/0x38 returned 0 after 0 usecs
>
>This will confuse tools such as scripts/bootgraph.pl.
>
>Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com>
>Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
these 3 patches are also available at:
http://gitorious.org/usb/usb/commits/clksource
to pull in the patches use:
git pull git://gitorious.org/usb/usb.git clksource
--
balbi
next prev parent reply other threads:[~2010-04-07 10:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 11:13 [RFC/PATCH 0/3] 32k timer patches Felipe Balbi
2010-03-31 11:13 ` [RFC/PATCH 1/3] omap: fix clocksource_32k to start from zero Felipe Balbi
2010-03-31 11:13 ` [RFC/PATCH 2/3] arm: omap1: remove dead code from timer32k.c Felipe Balbi
2010-04-06 21:30 ` Kevin Hilman
2010-03-31 11:13 ` [RFC/PATCH 3/3] arm: omap1/2/3/4: convert clocksource to a platform_driver Felipe Balbi
2010-04-06 21:37 ` Kevin Hilman
2010-04-07 7:21 ` Felipe Balbi
2010-04-07 9:57 ` [PATCH 1/3] omap: fix clocksource_32k to start from zero felipe.balbi
2010-04-07 10:02 ` Felipe Balbi [this message]
2010-04-22 23:49 ` [APPLIED] " Tony Lindgren
2010-04-07 9:57 ` [PATCH 2/3] arm: omap1: remove dead code from timer32k.c felipe.balbi
2010-04-22 23:49 ` [APPLIED] " Tony Lindgren
2010-04-07 9:57 ` [PATCH 3/3] arm: omap1/2/3/4: convert 32k-sync driver to a platform_driver felipe.balbi
2010-04-07 16:08 ` Kevin Hilman
2010-04-07 17:34 ` Felipe Balbi
2010-06-11 15:24 ` Shilimkar, Santosh
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=20100407100231.GY16297@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=aaro.koskinen@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).