From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM i.MX25: clk: parent per5_clk to AHB clock
Date: Wed, 30 Jan 2013 10:53:53 +0100 [thread overview]
Message-ID: <20130130095353.GI8668@pengutronix.de> (raw)
In-Reply-To: <1359538435-21304-1-git-send-email-s.trumtrar@pengutronix.de>
On Wed, Jan 30, 2013 at 10:33:55AM +0100, Steffen Trumtrar wrote:
> The mxc-timer on the imx25 needs to be derived from the AHB clock.
> If a bootloader reparents this clock to the ipg_clk_highfreq, which according
> to the datasheet is a valid operation, the system can/will produce lockups/
> freezes after some time [1].
>
> This can be forced with code like
> while(1)
> syscall(SYS_clock_gettime, CLOCK_REALTIME, &tp);
>
> This was already fixed with the commit
> "i.MX25 GPT clock fix: ensure correct the clock source" [2],
> but it seems, that it got lost. So, re-add this to have a correct gpt.
>
> [1]: http://lists.arm.linux.org.uk/lurker/message/20130129.161230.229bda17.en.html
> [2]: 2012d9ca2a1381ae3e733330a7f0d1d2f1988bba
Instead of the last paragraph I'd write:
This problem was already fixed with commit
2012d9c (i.MX25 GPT clock fix: ensure correct the clock source)
for v3.1-rc2 but this was lost when i.MX was converted to the common
clock framework (commit 6bbaec5; ARM i.MX25: implement clocks using
common clock framework).
> Signed-off-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
> Cc: stable at vger.kernel.org
Cc: stable at vger.kernel.org # v3.5+
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-01-30 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 9:33 [PATCH] ARM i.MX25: clk: parent per5_clk to AHB clock Steffen Trumtrar
2013-01-30 9:53 ` Uwe Kleine-König [this message]
2013-01-30 13:10 ` Steffen Trumtrar
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=20130130095353.GI8668@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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 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).