From: Guenter Roeck <linux@roeck-us.net>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
wim@iguana.be, nsekhar@ti.com, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, Pawel.Moll@arm.com,
swarren@wwwdotorg.org, ijc+devicetree@hellion.org.uk,
galak@kernel.crashing.org, rob.herring@calxeda.com,
linux-kernel@vger.kernel.org, grant.likely@linaro.org,
grygorii.strashko@ti.com
Subject: Re: [PATCH v5 1/5] watchdog: davinci: change driver to use WDT core
Date: Wed, 4 Dec 2013 12:48:18 -0800 [thread overview]
Message-ID: <20131204204818.GA3096@roeck-us.net> (raw)
In-Reply-To: <1386185970-14488-2-git-send-email-ivan.khoronzhuk@ti.com>
On Wed, Dec 04, 2013 at 09:39:26PM +0200, Ivan Khoronzhuk wrote:
> To reduce code duplicate and increase code readability use WDT core
> code to handle WDT interface.
>
> Remove io_lock as the WDT core uses mutex to lock each wdt device.
> Remove wdt_state as the WDT core tracks state with its own variable.
>
> The watchdog_init_timeout() can read timeout value from timeout-sec
> property if the passed value is out of bounds. The heartbeat is
> initialized in next way. If heartbeat is not set thought module
> parameter, try to read it's value from WDT node timeout-sec property.
> If node has no one, use default value.
>
> The heartbeat is hold in wdd->timeout by WDT core, so use it in
> order to set timeout period.
>
> Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Looks good, except you did not explain ...
>
> - dev_info(dev, "heartbeat %d sec\n", heartbeat);
> + watchdog_set_nowayout(wdd, 1);
>
why nowayout is enforced.
Thanks,
Guenter
next prev parent reply other threads:[~2013-12-04 20:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 19:39 [PATCH v5 0/5] Update Davinci watchdog driver Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 1/5] watchdog: davinci: change driver to use WDT core Ivan Khoronzhuk
2013-12-04 20:48 ` Guenter Roeck [this message]
2013-12-05 11:26 ` [PATCH v6 " Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 2/5] watchdog: davinci: use davinci_wdt_device structure to hold device data Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 3/5] watchdog: davinci: add GET_TIMELEFT option support Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 4/5] watchdog: davinci: add "timeout-sec" property Ivan Khoronzhuk
2013-12-04 19:39 ` [PATCH v5 5/5] watchdog: davinci: reuse driver for keystone arch Ivan Khoronzhuk
2013-12-09 16:27 ` [PATCH v5 0/5] Update Davinci watchdog driver Santosh Shilimkar
2013-12-14 19:17 ` Santosh Shilimkar
2013-12-26 17:55 ` Santosh Shilimkar
2013-12-26 18:17 ` Wim Van Sebroeck
[not found] ` <20131226181725.GL10136-1F/o1hAF34+bEvaWgpTR7kEOCMrvLtNR@public.gmane.org>
2013-12-26 18:20 ` Santosh Shilimkar
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=20131204204818.GA3096@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--cc=santosh.shilimkar@ti.com \
--cc=swarren@wwwdotorg.org \
--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;
as well as URLs for NNTP newsgroup(s).