From: Oleksij Rempel <linux@rempel-privat.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, wim@iguana.be
Subject: Re: [PATCH] watchdog: add Alphascale asm9260-wdt driver
Date: Thu, 29 Oct 2015 08:20:09 +0100 [thread overview]
Message-ID: <5631C8A9.3050602@rempel-privat.de> (raw)
In-Reply-To: <20151027023132.GA1270@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 3415 bytes --]
Hi,
thank you for your time.
Am 27.10.2015 um 03:31 schrieb Guenter Roeck:
> On Fri, Sep 18, 2015 at 11:23:32AM +0200, Oleksij Rempel wrote:
>> Add WD support for Alphascale asm9260 SoC. This driver
>> provide support for different function modes:
>> - HW mode to trigger SoC reset on timeout
>> - SW mode do soft reset if needed
>> - DEBUG mode
>>
>> Optional support for stopping watchdog. If reset binding are not provided
>> this driver will work in nowayout mode.
>
> Why ?
Because this controller can't be stopped. Only way to stop it is to
reset it from reset controller, which is out of scope of this driver.
On other side i can make reset binding as required...
>>
>> Signed-off-by: Oleksij Rempel <linux@rempel-privat.de>
>> ---
>> .../bindings/watchdog/alphascale-asm9260.txt | 38 ++
>> drivers/watchdog/Kconfig | 9 +
>> drivers/watchdog/Makefile | 1 +
>> drivers/watchdog/asm9260_wdt.c | 405 +++++++++++++++++++++
>> 4 files changed, 453 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/watchdog/alphascale-asm9260.txt
>> create mode 100644 drivers/watchdog/asm9260_wdt.c
>>
>> diff --git a/Documentation/devicetree/bindings/watchdog/alphascale-asm9260.txt b/Documentation/devicetree/bindings/watchdog/alphascale-asm9260.txt
>> new file mode 100644
>> index 0000000..cbe388b
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/watchdog/alphascale-asm9260.txt
>> @@ -0,0 +1,38 @@
>> +Alphascale asm9260 Watchdog timer
>> +
>> +Required properties:
>> +
>> +- compatible : should be "alphascale,asm9260-wdt".
>> +- reg : Specifies base physical address and size of the registers.
>> +- clocks : the clock feeding the watchdog timer.
>
> There are two -> clocks.
>
>> + Needed if platform uses clocks. See clock-bindings.txt
>
> The rest of the code suggests that the clocks are mandatory.
> probe fails if asm9260_wdt_get_dt_clks() returns an error,
> and the clock frequency would be 0.
>
>> +- clock-names : should be set to
>> + "mod" - source for tick counter.
>> + "ahb" - ahb gate.
>> +
>> +Optional properties:
>> +- resets : phandle pointing to the system reset controller with correct
>> + reset line index for watchdog controller reset. This propertie is
>> + required if you need to disable "nowayout" and it works only with
>> + CONFIG_WATCHDOG_NOWAYOUT=n.
>> +- reset-names : should be set to "wdt_rst" if "resets" is used.
>> +- timeout-sec : shall contain the default watchdog timeout in seconds,
>> + if unset, the default timeout is 30 seconds.
>> +- alphascale,mode : tree modes are supported
>> + "hw" - hw reset (defaul).
>> + "sw" - sw reset.
>> + "debug" - no action is taken.
>> +
>> +Example:
>> +
>> +watchdog0: watchdog@80048000 {
>> + compatible = "alphascale,asm9260-wdt";
>> + reg = <0x80048000 0x10>;
>> + clocks = <&acc CLKID_SYS_WDT>, <&acc CLKID_AHB_WDT>;
>> + clock-names = "mod", "ahb";
>> + interrupts = <55>;
>> + resets = <&rst WDT_RESET>;
>> + reset-names = "wdt_rst";
>> + timeout-sec = <30>;
>> + alphascale,mode = "hw"
>
> Seems to miss a ';'.
>
> Did you get any feedback from dt maintainers on those bindings ?
No, i'll CC updated patch to devicetree list.
Thank you for other comments, i'll take care of it.
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2015-10-29 7:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 9:23 [PATCH] watchdog: add Alphascale asm9260-wdt driver Oleksij Rempel
2015-10-20 7:49 ` Oleksij Rempel
2015-10-26 12:31 ` Guenter Roeck
2015-10-27 2:31 ` Guenter Roeck
2015-10-29 7:20 ` Oleksij Rempel [this message]
2015-11-05 9:06 ` [PATCH v2] " Oleksij Rempel
2015-11-05 9:06 ` [PATCH v2] watchdog: " Oleksij Rempel
2015-11-05 16:32 ` Guenter Roeck
2015-11-05 20:43 ` Rob Herring
2015-11-23 7:11 ` Oleksij Rempel
2015-11-23 7:26 ` Guenter Roeck
2015-11-23 9:51 ` Oleksij Rempel
2015-11-23 15:47 ` Guenter Roeck
2015-11-24 21:40 ` [PATCH v3 0/2] " Oleksij Rempel
2015-11-24 21:40 ` [PATCH v3 1/2] watchdog: " Oleksij Rempel
2015-11-25 3:22 ` Guenter Roeck
2015-11-24 21:40 ` [PATCH v3 2/2] DT: watchdog: add Alphascale asm9260 watchdog binding documentation Oleksij Rempel
2015-11-25 20:06 ` Rob Herring
2015-11-25 19:33 ` [PATCH v4 0/2] add Alphascale asm9260-wdt driver Oleksij Rempel
2015-11-25 19:33 ` [PATCH v4 1/2] watchdog: " Oleksij Rempel
2015-11-30 16:10 ` Guenter Roeck
2015-11-30 16:10 ` Guenter Roeck
2015-11-25 19:33 ` [PATCH v4 2/2] DT: watchdog: add Alphascale asm9260 watchdog binding documentation Oleksij Rempel
2015-12-28 21:49 ` [PATCH v4 0/2] add Alphascale asm9260-wdt driver Wim Van Sebroeck
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=5631C8A9.3050602@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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