From: Jean Delvare <jdelvare@suse.de>
To: linux-watchdog@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>,
Justin Chen <justinpopo6@gmail.com>,
Wim Van Sebroeck <wim@iguana.be>
Subject: [PATCH v2] watchdog: Add hardware dependency to BCM7038 driver
Date: Wed, 24 Feb 2016 16:17:26 +0100 [thread overview]
Message-ID: <20160224161726.4888edd4@endymion> (raw)
The BCM7038 watchdog driver is specific to Broadcom ARM and MIPS
SoCs so do not present it on other architectures, unless
build-testing.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Justin Chen <justinpopo6@gmail.com>
Cc: Wim Van Sebroeck <wim@iguana.be>
---
Changes since v1:
* Better dependencies, suggested by Justin, and updated the
description accordingly.
* Better option description, provided by Justin.
drivers/watchdog/Kconfig | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
--- linux-4.5-rc5.orig/drivers/watchdog/Kconfig 2016-02-24 14:43:18.943460233 +0100
+++ linux-4.5-rc5/drivers/watchdog/Kconfig 2016-02-24 15:42:49.756057691 +0100
@@ -1377,10 +1377,12 @@ config BCM7038_WDT
tristate "BCM7038 Watchdog"
select WATCHDOG_CORE
depends on HAS_IOMEM
+ depends on ARCH_BRCMSTB || BMIPS_GENERIC || COMPILE_TEST
help
- Watchdog driver for the built-in hardware in Broadcom 7038 SoCs.
-
- Say 'Y or 'M' here to enable the driver.
+ Watchdog driver for the built-in hardware in Broadcom 7038 and
+ later SoCs used in set-top boxes. BCM7038 was made public
+ during the 2004 CES, and since then, many Broadcom chips use this
+ watchdog block, including some cable modem chips.
config IMGPDC_WDT
tristate "Imagination Technologies PDC Watchdog Timer"
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2016-02-24 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 15:17 Jean Delvare [this message]
2016-02-24 15:30 ` [PATCH v2] watchdog: Add hardware dependency to BCM7038 driver Guenter Roeck
2016-02-24 17:08 ` Justin Chen
2016-03-04 19:37 ` 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=20160224161726.4888edd4@endymion \
--to=jdelvare@suse.de \
--cc=justinpopo6@gmail.com \
--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