From: Timur Tabi <timur@codeaurora.org>
To: Fu Wei <fu.wei@linaro.org>, Guenter Roeck <linux@roeck-us.net>
Cc: Linaro ACPI Mailman List <linaro-acpi@lists.linaro.org>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>,
Jon Masters <jcm@redhat.com>, Pratyush Anand <panand@redhat.com>,
Will Deacon <will.deacon@arm.com>,
Wim Van Sebroeck <wim@iguana.be>,
Catalin Marinas <catalin.marinas@arm.com>,
Wei Fu <tekkamanninja@gmail.com>,
Rob Herring <robherring2@gmail.com>,
Vipul Gandhi <vgandhi@codeaurora.org>,
Dave Young <dyoung@redhat.com>
Subject: Re: [Linaro-acpi] [PATCH v8 5/5] Watchdog: introduce ARM SBSA watchdog driver
Date: Thu, 5 Nov 2015 07:47:04 -0600 [thread overview]
Message-ID: <563B5DD8.901@codeaurora.org> (raw)
In-Reply-To: <CADyBb7tTf0Jz0sgKecSn-LgMEUMdueTb5Uxq_e5t39byOsJQEQ@mail.gmail.com>
Fu Wei wrote:
> (1)It is not new.
> pre-timeout concept has been used by two drivers before this driver.
> and this concept has been in kernel documentation.
It's "new" in that it's a new infrastructure. The private API of two
other drivers doesn't count.
> (1) if we don't, for this two stages timeout, we have to config them
> by one value.
> that means "the first stage timeout" have to be equal to "the second
> stage timeout",
> For example, if we need 60 second for "the second stage timeout", 30
> or less for "the first stage timeout".
> then "the first stage timeout" have to be 60s too. I don't think it 's
> good idea.
Why do we care about two stages? Don't have a pre-timeout, and just
have one stage: the WS1 reset. Ignore the WS0 interrupt, and program
the timeout so that WS1 is the reset.
I'm not saying that pre-timeout is a terrible idea and we should never
do it. I'm saying that it's not an important feature, and we should
only support it to the extent that the hardware provides the feature.
We should definitely not make the driver more complicated and less safe.
If we agree that an SBSA watchdog allows for a pre-timeout at half-way
through timeout, and that software can't change this, then we can use
WS0 as the pre-timeout and applications just have to deal with that.
The hardware is programmed to reset via WS1, and all we do in the
interrupt handler is notify the application that a pre-timeout has
occurred.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
next prev parent reply other threads:[~2015-11-05 13:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:06 [PATCH v8 0/5] Watchdog: introduce ARM SBSA watchdog driver fu.wei
2015-10-27 16:06 ` [PATCH v8 1/5] Documentation: add sbsa-gwdt driver documentation fu.wei
2015-10-27 16:22 ` Mark Rutland
2015-10-28 4:10 ` Fu Wei
2015-10-30 17:46 ` Timur Tabi
2015-10-30 18:35 ` Fu Wei
2015-10-30 18:53 ` Timur Tabi
2015-10-30 19:05 ` Mark Rutland
2015-10-30 20:37 ` Timur Tabi
2015-11-02 4:10 ` Fu Wei
2015-11-02 4:03 ` Fu Wei
2015-11-02 4:06 ` Timur Tabi
2015-11-02 4:23 ` Jon Masters
2015-10-27 16:06 ` [PATCH v8 2/5] ARM64: add SBSA Generic Watchdog device node in foundation-v8.dts fu.wei
2015-10-27 16:06 ` [PATCH v8 3/5] ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi fu.wei
2015-10-27 16:06 ` [PATCH v8 4/5] Watchdog: introdouce "pretimeout" into framework fu.wei
2015-10-27 16:06 ` [PATCH v8 5/5] Watchdog: introduce ARM SBSA watchdog driver fu.wei
2015-11-05 1:59 ` [Linaro-acpi] " Timur Tabi
2015-11-05 5:13 ` Guenter Roeck
2015-11-05 11:58 ` Fu Wei
2015-11-05 13:47 ` Timur Tabi [this message]
2015-11-05 13:47 ` Timur Tabi
2015-11-05 14:03 ` Fu Wei
2015-11-05 14:08 ` Timur Tabi
2015-11-05 14:35 ` Fu Wei
2015-11-05 14:40 ` Timur Tabi
2015-11-05 15:00 ` Fu Wei
2015-11-05 16:41 ` Guenter Roeck
2015-11-05 17:58 ` Fu Wei
2015-11-05 17:59 ` Timur Tabi
2015-11-05 18:04 ` Fu Wei
2015-11-13 0:06 ` Al Stone
2015-11-13 0:23 ` Timur Tabi
2015-11-19 23:50 ` Al Stone
2015-11-13 0:25 ` Guenter Roeck
2015-11-20 0:11 ` Al Stone
2015-11-20 0:26 ` Timur Tabi
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=563B5DD8.901@codeaurora.org \
--to=timur@codeaurora.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=dyoung@redhat.com \
--cc=fu.wei@linaro.org \
--cc=jcm@redhat.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=panand@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=robherring2@gmail.com \
--cc=tekkamanninja@gmail.com \
--cc=vgandhi@codeaurora.org \
--cc=will.deacon@arm.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