From: boris brezillon <b.brezillon@overkiz.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Landley <rob@landley.net>,
Russell King <linux@arm.linux.org.uk>,
Fabio Porcedda <fabio.porcedda@gmail.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Guenter Roeck <groeck7@gmail.com>,
Yang Wenyou <wenyou.yang@atmel.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v5 0/4] watchdog: at91sam9_wdt: handle already configured wdt
Date: Tue, 29 Oct 2013 11:31:37 +0100 [thread overview]
Message-ID: <526F8E89.30005@overkiz.com> (raw)
In-Reply-To: <20131029075028.GF19704@spo001.leaseweb.com>
Hi Wim,
I'm sorry for the inconvenience, but I found some bugs in my patch series:
1) the secs_to_ticks returns an erronous value when 0 is passed as an
argument
2) the calculated heartbeat is too small for some use cases
(i.e. kexecing a new kernel might trigger a watchdog reset before
the new kernel
is able to load the watchdog driver)
3) when initializing the watchdog driver, the timer should be configured
with the min_heartbeat value
instead of the standard heartbeat value, because we don't for how
long the timer has been running.
I'll send a new patch fixing those issues.
I hope it won't bother you :-(.
Best Regards,
Boris
On 29/10/2013 08:50, Wim Van Sebroeck wrote:
> Hi Boris,
>
>> Hello,
>>
>> This patch series is a porposal to enhance the sam9 watchdog timer support.
>>
>> The at91sam9 watchdog timer can only be configured once, and the current
>> implementation tries to configure it in a static way:
>> - 2 seconds timeout
>> - wdt restart every 500ms
>>
>> If the timer has already been configured with different values, it returns an
>> error and do not create any watchdog device.
>>
>> This is not critical if the watchdog is disabled, but if it has been enabled
>> with different timeout values it will lead to a SoC reset.
>>
>> This patch series tries to address this issue by adapting the heartbeat value
>> according the WDT timer config:
>> - it first tries to configure the timer as requested.
>> - if it fails it fallbacks to the current config, adapting its heartbeat timer
>> to the needs
>>
>> This patch series also move to a dynamically allocated at91wdt device instead
>> of the static instance. I'm not sure this is the best solution, so please tell
>> me if you prefer to keep static instance of watchdog.
>>
>> It adds a new at91 wdt type: software. This new type make use of the at91 wdt
>> interrupt to trigger a software reboot.
>>
>> Finally it adds several properties to the device tree bindings.
>>
>> Best Regards,
>> Boris
>>
>> Changes since v4:
>> - fix coding style issues
>> - remove unneeded watchdog_active test
>>
>> Changes since v3:
>> - fix a bug in heartbeat time computation
>> - fix a bug in at91_wdt_set_timeout when new timeout is bigger than the old
>> one
>> - rename at91_wdt_ping into at91_wdt_start
>> - remove unneeded ping callback assignment
>>
>> Changes since v2:
>> - fix documentation
>> - rework the heartbeat computation to get a more flexible behaviour
>> - fix xx_to_yy macros
>> - modify warning and error messages
>> - remove unneeded parenthesis in arithmetic operations
>> - use devm functions to map io memory
>> - remove unneeded devm_kfree calls
>>
>> Change since v1:
>> - fix typo in documentaion
>> - fix irq dt definition for sama5d3 SoC
>>
>>
>> Boris BREZILLON (4):
>> watchdog: at91sam9_wdt: better watchdog support
>> watchdog: at91sam9_wdt: update device tree doc
>> ARM: at91/dt: add sam9 watchdog default options to SoCs
>> ARM: at91/dt: add watchdog properties to kizbox board
>>
>> .../devicetree/bindings/watchdog/atmel-wdt.txt | 30 +-
>> arch/arm/boot/dts/at91sam9260.dtsi | 5 +
>> arch/arm/boot/dts/at91sam9263.dtsi | 5 +
>> arch/arm/boot/dts/at91sam9g45.dtsi | 5 +
>> arch/arm/boot/dts/at91sam9n12.dtsi | 5 +
>> arch/arm/boot/dts/at91sam9x5.dtsi | 5 +
>> arch/arm/boot/dts/kizbox.dts | 6 +
>> arch/arm/boot/dts/sama5d3.dtsi | 5 +
>> drivers/watchdog/at91sam9_wdt.c | 309 ++++++++++++++------
>> 9 files changed, 287 insertions(+), 88 deletions(-)
> These 4 patches have been added to linux-watchdog-next.
>
> Kind regards,
> Wim.
>
next prev parent reply other threads:[~2013-10-29 10:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 7:24 [PATCH v5 0/4] watchdog: at91sam9_wdt: handle already configured wdt Boris BREZILLON
2013-10-04 7:24 ` [PATCH v5 1/4] watchdog: at91sam9_wdt: better watchdog support Boris BREZILLON
2013-10-04 22:30 ` Guenter Roeck
2013-10-04 7:24 ` [PATCH v5 2/4] watchdog: at91sam9_wdt: update device tree doc Boris BREZILLON
2013-10-04 22:30 ` Guenter Roeck
2013-10-04 7:24 ` [PATCH v5 3/4] ARM: at91/dt: add sam9 watchdog default options to SoCs Boris BREZILLON
2013-10-04 22:31 ` Guenter Roeck
2013-10-04 7:24 ` [PATCH v5 4/4] ARM: at91/dt: add watchdog properties to kizbox board Boris BREZILLON
2013-10-04 22:32 ` Guenter Roeck
2013-10-29 7:50 ` [PATCH v5 0/4] watchdog: at91sam9_wdt: handle already configured wdt Wim Van Sebroeck
2013-10-29 10:31 ` boris brezillon [this message]
2013-10-29 12:58 ` Wim Van Sebroeck
2013-10-29 13:25 ` boris brezillon
2013-10-29 10:37 ` [PATCH] watchdog: at91sam9_wdt: various fixes Boris BREZILLON
2013-10-29 15:45 ` Guenter Roeck
2013-10-29 16:22 ` boris brezillon
2013-10-29 16:43 ` Guenter Roeck
2013-10-29 17:22 ` boris brezillon
2013-10-29 21:27 ` Guenter Roeck
2013-10-30 6:01 ` b.brezillon
2013-10-31 10:13 ` Jean-Christophe PLAGNIOL-VILLARD
2013-11-03 14:42 ` boris brezillon
2013-11-03 16:22 ` Guenter Roeck
2013-11-03 17:55 ` boris brezillon
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=526F8E89.30005@overkiz.com \
--to=b.brezillon@overkiz.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.porcedda@gmail.com \
--cc=groeck7@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.org \
--cc=wenyou.yang@atmel.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;
as well as URLs for NNTP newsgroup(s).