mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: linux@roeck-us.net (Guenter Roeck)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v3 5/7] watchdog: mtk: allow setting timeout in devicetree
Date: Sun, 18 Feb 2018 17:08:32 -0800	[thread overview]
Message-ID: <46ff7605-5166-477b-85b1-7d2f53f7c57b@roeck-us.net> (raw)
In-Reply-To: <20180219000835.ualdfczfsnjzqr6d@rob-hp-laptop>

On 02/18/2018 04:08 PM, Rob Herring wrote:
> On Sun, Feb 11, 2018 at 09:08:45PM +0100, Marcus Folkesson wrote:
>> watchdog_init_timeout() will allways pick timeout_param since it
>> defaults to a valid timeout.
>>
>> By following best practice described in
>> Documentation/watchdog/watchdog-kernel-api.txt, it also
>> let us to set timout-sec property in devicetree.
> 
> Same problems in this one.
> 

Same answer. In the existing driver;

         mtk_wdt->wdt_dev.timeout = WDT_MAX_TIMEOUT;

Guenter

>>
>> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>>   Documentation/devicetree/bindings/watchdog/mtk-wdt.txt | 4 ++++
>>   drivers/watchdog/mtk_wdt.c                             | 2 +-
>>   2 files changed, 5 insertions(+), 1 deletion(-)
> 

  reply	other threads:[~2018-02-19  1:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-11 20:08 [PATCH v3 1/7] watchdog: sama5d4: make use of timeout-secs provided " Marcus Folkesson
2018-02-11 20:08 ` [PATCH v3 2/7] watchdog: sunxi: allow setting timeout " Marcus Folkesson
2018-02-19  0:06   ` Rob Herring
2018-02-19  3:01     ` Chen-Yu Tsai
2018-02-11 20:08 ` [PATCH v3 3/7] watchdog: sirfsoc: " Marcus Folkesson
2018-02-19  0:07   ` Rob Herring
2018-02-19  1:07     ` Guenter Roeck
2018-02-22  0:02       ` Rob Herring
2018-02-11 20:08 ` [PATCH v3 4/7] watchdog: pnx4008: make use of timeout-secs provided " Marcus Folkesson
2018-02-11 20:08 ` [PATCH v3 5/7] watchdog: mtk: allow setting timeout " Marcus Folkesson
2018-02-19  0:08   ` Rob Herring
2018-02-19  1:08     ` Guenter Roeck [this message]
2018-02-19 17:02   ` Matthias Brugger
2018-02-11 20:08 ` [PATCH v3 6/7] watchdog: meson: " Marcus Folkesson
2018-02-11 20:08 ` [PATCH v3 7/7] watchdog: coh901327: make use of timeout-secs provided " Marcus Folkesson
2018-02-12  1:11   ` [v3, " Guenter Roeck
2018-02-22 14:01   ` [PATCH v3 " Linus Walleij
2018-02-12  1:10 ` [v3, 1/7] watchdog: sama5d4: " Guenter Roeck
2018-02-12  8:59 ` [PATCH v3 " Nicolas Ferre
2018-03-16 13:37 ` Marcus Folkesson
2018-03-17  1:56   ` Guenter Roeck
2018-03-17  8:37     ` Marcus Folkesson

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=46ff7605-5166-477b-85b1-7d2f53f7c57b@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linus-amlogic@lists.infradead.org \
    /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

all inboxes | Powered by JetHome®