From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Vitaly Kuzmichev <vkuzmichev@mvista.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Wim Van Sebroeck <wim@iguana.be>,
Marc Zyngier <marc.zyngier@arm.com>,
Colin Cross <ccross@android.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/4] ARM: smp_twd: Fix typo in 'twd_timer_rate' printing
Date: Sun, 10 Jul 2011 11:47:40 +0100 [thread overview]
Message-ID: <20110710104740.GD4812@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4E15DCE1.8010201@mvista.com>
On Thu, Jul 07, 2011 at 08:20:49PM +0400, Vitaly Kuzmichev wrote:
> Hi Russell,
>
> On 07/07/2011 04:39 PM, Russell King - ARM Linux wrote:
> > On Thu, Jul 07, 2011 at 04:23:13PM +0400, Vitaly Kuzmichev wrote:
> >> To get hundredths of MHz the rate needs to be divided by 10'000.
> >> Here is an example:
> >> twd_timer_rate = 123456789
> >> Before the patch:
> >> twd_timer_rate / 1000000 = 123
> >> (twd_timer_rate / 1000000) % 100 = 23
> >> Result: 123.23MHz.
> >> After being fixed:
> >> twd_timer_rate / 1000000 = 123
> >> (twd_timer_rate / 10000) % 100 = 45
> >> Result: 123.45MHz.
> >>
> >> Signed-off-by: Vitaly Kuzmichev <vkuzmichev@mvista.com>
> >
> > -> patch system please.
>
> Should I submit other patches into this system too?
No, the other patches I've yet to look at, and I think there's issues
still to be resolved.
Eg, ISTR a patch to make smp_twd.c selectable on non-SMP platforms so
that the mpcore watchdog can be used on non-SMP platforms. While that
fixes the build issues, functionally its broken. I don't think that
the mpcore watchdog should be asking the smp_twd code in any case for
the clock rate.
If we get the issue with knowing the TWD clock rate on ARMs development
platforms sorted out, then we can provide a struct clk for it, which
means everyone can finally move to using the clk API to get the mpcore
watchdog/twd clock rate.
next prev parent reply other threads:[~2011-07-10 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310041339-2348-1-git-send-email-vkuzmichev@mvista.com>
[not found] ` <1310041396-2461-1-git-send-email-vkuzmichev@mvista.com>
[not found] ` <20110707123907.GP8286@n2100.arm.linux.org.uk>
2011-07-07 16:20 ` [PATCH V3 1/4] ARM: smp_twd: Fix typo in 'twd_timer_rate' printing Vitaly Kuzmichev
2011-07-10 10:47 ` Russell King - ARM Linux [this message]
2011-07-11 11:50 ` Vitaly Kuzmichev
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=20110710104740.GD4812@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=ccross@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=vkuzmichev@mvista.com \
--cc=wim@iguana.be \
/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