From: Tommy Lin <tommy.lin.1101@gmail.com>
To: "'Anton Vorontsov'" <cbouatmailru@gmail.com>,
"'Tommy Lin'" <tommy.lin.1101@gmail.com>
Cc: "'Wim Van Sebroeck'" <wim@iguana.be>,
<linux-watchdog@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Lin, Mac" <Mac.Lin@caviumnetworks.com>
Subject: RE: [PATCH 2/2] watchdog: mpcore_wdt Add reload value setting for CNS3xxx hardware
Date: Wed, 6 Jul 2011 18:05:37 +0800 [thread overview]
Message-ID: <281B1F8BAB4D4BDABE7568809A0AEC1A@starsemi.com> (raw)
In-Reply-To: <20110705140559.GA15771@oksana.dev.rtsoft.ru>
Hi, I just found another patch that can solve the watchdog counter reload
issue. Please ignore this patch, since it should not acceptable to use
#ifdefs.
From Vitaly Kuzmichev <vkuzmichev@mvista.com>
Subject [PATCH V2 2/6] arm_smp_twd: mpcore_wdt: Fix watchdog counter loading
Date Tue, 5 Jul 2011 23:00:36 +0400
--
Tommy Lin
-----Original Message-----
From: Anton Vorontsov [mailto:cbouatmailru@gmail.com]
Sent: Tuesday, July 05, 2011 10:06 PM
To: Tommy Lin
Cc: Wim Van Sebroeck; linux-watchdog@vger.kernel.org;
linux-kernel@vger.kernel.org; mac.lin@caviumnetworks.com; Tommy Lin
Subject: Re: [PATCH 2/2] watchdog: mpcore_wdt Add reload value setting for
CNS3xxx hardware
Hello,
thanks for the patches.
On Tue, Jul 05, 2011 at 08:05:48PM +0800, Tommy Lin wrote:
> Original MPcore watchdog setting about load register (offset 0x20) is
different
> from CNS3xxx data sheet. The CNS3xxx data sheet says watchdog has
following
> features:
> 1. The Watchdog Counter Register (offset 0x24) is a down counter.
> 2. The timer interval is calculated using following equation:
> (PRESCALER_value+1) X (Load_value+1) X 2 / CPU CLK_frequency
> Thus the watchdog load register control in CNS3xxx way is add to MPcore
watchdog
> source. The original control method is also kept if the CPU architecture
is not
> CNS3xxx.
>
> Signed-off-by: Tommy Lin <tommy.lin@caviumnetworks.com>
> ---
> drivers/watchdog/mpcore_wdt.c | 12 ++++++++++++
> 1 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/watchdog/mpcore_wdt.c b/drivers/watchdog/mpcore_wdt.c
> index 2b4af22..816e0c5 100644
> --- a/drivers/watchdog/mpcore_wdt.c
> +++ b/drivers/watchdog/mpcore_wdt.c
> @@ -42,6 +42,9 @@ struct mpcore_wdt {
> int irq;
> unsigned int perturb;
> char expect_close;
> +#ifdef CONFIG_ARCH_CNS3XXX
> + unsigned long reload_unit; /* ticks per second */
> +#endif
Nope, these #ifdefs are not acceptible. Kernel should support multi-arch
images soon.
[...]
> +#ifdef CONFIG_ARCH_CNS3XXX
> + /* Assume prescale is set to 256 */
> + wdt->reload_unit = cns3xxx_cpu_clock() * 1000000 / 256 / 2;
> +#endif
You probably want to pass reload_unit via platform_data, and also
check (in runtime) that the watchdog is CNS3xxx. Or if reload_unit
!= 0.
Thanks,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2011-07-06 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 12:05 Tommy Lin
2011-07-05 14:05 ` Anton Vorontsov
2011-07-06 10:05 ` Tommy Lin [this message]
2011-07-06 11:16 ` Anton Vorontsov
2011-07-06 11:28 ` Anton Vorontsov
2011-07-06 11:46 ` Anton Vorontsov
2011-07-06 14:54 ` Lin, Tommy
2011-07-06 19:34 ` Anton Vorontsov
2011-07-08 7:28 ` Tommy Lin
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=281B1F8BAB4D4BDABE7568809A0AEC1A@starsemi.com \
--to=tommy.lin.1101@gmail.com \
--cc=Mac.Lin@caviumnetworks.com \
--cc=cbouatmailru@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=tommy.lin@caviumnetworks.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
all inboxes | Powered by JetHome®