From: Timur Tabi <timur@codeaurora.org>
To: Guenter Roeck <linux@roeck-us.net>, Pratyush Anand <panand@redhat.com>
Cc: linux-watchdog@vger.kernel.org, kexec@lists.infradead.org,
open list <linux-kernel@vger.kernel.org>,
wim@iguana.be, fu.wei@linaro.org, Suravee.Suthikulpanit@amd.com,
Dave Young <dyoung@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] Watchdog: sbsa_gwdt: Enhance timeout range
Date: Thu, 5 May 2016 18:38:01 -0500 [thread overview]
Message-ID: <572BD959.3090507@codeaurora.org> (raw)
In-Reply-To: <572BD8E3.4070707@roeck-us.net>
Guenter Roeck wrote:
> A 32-bit counter is absolutely fine. Letting it run with a 400MHz clock
> (or was it 200 MHz ?) is the problem. A resolution of 2.5ns for a watchdog
> timer does not really make any sense.
The 10 second limit is based on a 20MHz clock.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation collaborative project.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-05-05 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5728A7C3.4010001@roeck-us.net>
[not found] ` <20160503143856.GE13045@dhcppc6.redhat.com>
[not found] ` <5728BEC4.6050603@codeaurora.org>
[not found] ` <20160503155141.GF13045@dhcppc6.redhat.com>
[not found] ` <20160503171602.GA2518@roeck-us.net>
[not found] ` <20160504141449.GG13045@dhcppc6.redhat.com>
[not found] ` <572A0577.1070000@codeaurora.org>
[not found] ` <20160504155932.GH13045@dhcppc6.redhat.com>
[not found] ` <572A2099.4070901@codeaurora.org>
[not found] ` <20160505164300.GA16914@roeck-us.net>
2016-05-05 18:20 ` [PATCH RFC] Watchdog: sbsa_gwdt: Enhance timeout range Pratyush Anand
2016-05-05 18:22 ` Timur Tabi
2016-05-05 23:36 ` Guenter Roeck
2016-05-05 23:38 ` Timur Tabi [this message]
2016-05-05 23:45 ` Timur Tabi
2016-05-06 0:18 ` Guenter Roeck
2016-05-05 23:51 ` Guenter Roeck
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=572BD959.3090507@codeaurora.org \
--to=timur@codeaurora.org \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=dyoung@redhat.com \
--cc=fu.wei@linaro.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=panand@redhat.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