From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Improve timer Resolution on imx28
Date: Fri, 21 Dec 2012 15:52:17 +0100 [thread overview]
Message-ID: <201212211552.17744.marex@denx.de> (raw)
In-Reply-To: <1356098776-10498-1-git-send-email-torbenh@linutronix.de>
Dear Torben Hohn,
> Hi,
>
> this Series increases the timer frequency and decreases min_delta_ns.
> I saw pretty high max latencies with cyclictest: ~600us.
>
> The cause was the min_delta_ns value of 0xf 32kHz clockcycles.
> But with the 32kHz Clock, the period is still around 30us.
> So we just increase the clock freqeuncy driving the timers
> here.
Thanks for the set. Just a really quick question -- won't this under no
circumstance cause interrupt storm?
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-12-21 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 14:06 Improve timer Resolution on imx28 Torben Hohn
2012-12-21 14:06 ` [PATCH 1/2] mxs timer: use ahbx bus clock to drive the timers on timrotv2 Torben Hohn
2012-12-25 14:10 ` Shawn Guo
2012-12-21 14:06 ` [PATCH 2/2] mxs timer: decrease mxs_clockevent_device.min_delta_ns to 2 clock cycles Torben Hohn
2012-12-21 14:52 ` Marek Vasut [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=201212211552.17744.marex@denx.de \
--to=marex@denx.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).