Linux-Watchdog Archive on lore.kernel.org
 help / color / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-watchdog@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH 00/16] watchdog: refactor init_timeout and update users
Date: Sun, 14 Apr 2019 12:26:11 +0200
Message-ID: <20190414102627.5564-1-wsa+renesas@sang-engineering.com> (raw)

When trying to add DT support to the DA9063 WDT, I didn't want to add yet
another error message when watchdog_init_timeout fails. The core could do this
with more detail, and also much more consistent. So, I refactored this routine
and removed error strings from its callers. Note that DA9063 support is not
added here because I still need to think about another issue. But this series
has been tested using the renesas_wdt driver on a Renesas Salvator-XS board
(R-Car M3N) and build bot is happy, too.

Looking forward to comments.

Thanks,

   Wolfram

Wolfram Sang (16):
  watchdog: refactor watchdog_init_timeout
  watchdog: add error messages when initializing timeout fails
  watchdog: cadence_wdt: drop warning after calling
    watchdog_init_timeout
  watchdog: cadence_wdt: still probe if user supplied timeout is invalid
  watchdog: ebc-c384_wdt: drop warning after calling
    watchdog_init_timeout
  watchdog: hpwdt: drop warning after calling watchdog_init_timeout
  watchdog: i6300esb: drop warning after calling watchdog_init_timeout
  watchdog: imx_sc_wdt: drop warning after calling watchdog_init_timeout
  watchdog: ni903x_wdt: drop warning after calling watchdog_init_timeout
  watchdog: nic7018_wdt: drop warning after calling
    watchdog_init_timeout
  watchdog: renesas_wdt: drop warning after calling
    watchdog_init_timeout
  watchdog: sp5100_tco: drop warning after calling watchdog_init_timeout
  watchdog: st_lpc_wdt: drop warning after calling watchdog_init_timeout
  watchdog: stm32_iwdg: drop warning after calling watchdog_init_timeout
  watchdog: xen_wdt: drop warning after calling watchdog_init_timeout
  watchdog: ziirave_wdt: drop warning after calling
    watchdog_init_timeout

 drivers/watchdog/cadence_wdt.c   |  7 +------
 drivers/watchdog/ebc-c384_wdt.c  |  5 +----
 drivers/watchdog/hpwdt.c         |  3 +--
 drivers/watchdog/i6300esb.c      |  5 +----
 drivers/watchdog/imx_sc_wdt.c    |  5 +----
 drivers/watchdog/ni903x_wdt.c    |  4 +---
 drivers/watchdog/nic7018_wdt.c   |  5 +----
 drivers/watchdog/renesas_wdt.c   |  4 +---
 drivers/watchdog/sp5100_tco.c    |  4 +---
 drivers/watchdog/st_lpc_wdt.c    |  4 +---
 drivers/watchdog/stm32_iwdg.c    |  6 +-----
 drivers/watchdog/watchdog_core.c | 39 ++++++++++++++++++++++++---------------
 drivers/watchdog/xen_wdt.c       |  4 +---
 drivers/watchdog/ziirave_wdt.c   |  6 +-----
 14 files changed, 37 insertions(+), 64 deletions(-)

-- 
2.11.0


             reply index

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14 10:26 Wolfram Sang [this message]
2019-04-14 10:26 ` [PATCH 01/16] watchdog: refactor watchdog_init_timeout Wolfram Sang
2019-04-14 13:25   ` Guenter Roeck
2019-04-14 13:42     ` Wolfram Sang
2019-04-14 14:03       ` Guenter Roeck
2019-04-15  8:21   ` Sergei Shtylyov
2019-04-14 10:26 ` [PATCH 02/16] watchdog: add error messages when initializing timeout fails Wolfram Sang
2019-04-14 10:26 ` [PATCH 03/16] watchdog: cadence_wdt: drop warning after calling watchdog_init_timeout Wolfram Sang
2019-04-14 10:26 ` [PATCH 04/16] watchdog: cadence_wdt: still probe if user supplied timeout is invalid Wolfram Sang
2019-04-14 10:26 ` [PATCH 05/16] watchdog: ebc-c384_wdt: drop warning after calling watchdog_init_timeout Wolfram Sang
2019-04-14 10:26 ` [PATCH 06/16] watchdog: hpwdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 07/16] watchdog: i6300esb: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 08/16] watchdog: imx_sc_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 09/16] watchdog: ni903x_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 10/16] watchdog: nic7018_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 11/16] watchdog: renesas_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 12/16] watchdog: sp5100_tco: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 13/16] watchdog: st_lpc_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 14/16] watchdog: stm32_iwdg: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 15/16] watchdog: xen_wdt: " Wolfram Sang
2019-04-14 10:26 ` [PATCH 16/16] watchdog: ziirave_wdt: " Wolfram Sang
2019-04-14 10:30 ` [PATCH 00/16] watchdog: refactor init_timeout and update users Wolfram Sang
2019-04-14 15:41 ` Guenter Roeck

Reply instructions:

You may reply publically 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=20190414102627.5564-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.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

Linux-Watchdog Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-watchdog/0 linux-watchdog/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-watchdog linux-watchdog/ https://lore.kernel.org/linux-watchdog \
		linux-watchdog@vger.kernel.org
	public-inbox-index linux-watchdog

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-watchdog


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git