lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 18 Dec 2020 11:10:54 +0100
From:   Rasmus Villemoes <>
        Alexandre Belloni <>
        Rob Herring <>,
        Uwe Kleine-König 
        <>, Qiang Zhao <>,
        Bruno Thomsen <>,
        Rasmus Villemoes <>
Subject: [PATCH v3 2/2] rtc: pcf2127: only use watchdog when explicitly available

From: Uwe Kleine-König <>

Most boards using the pcf2127 chip (in my bubble) don't make use of the
watchdog functionality and the respective output is not connected. The
effect on such a board is that there is a watchdog device provided that
doesn't work.

So only register the watchdog if the device tree has a "reset-source"

Signed-off-by: Uwe Kleine-König <>
[RV: s/has-watchdog/reset-source/]
Signed-off-by: Rasmus Villemoes <>
 drivers/rtc/rtc-pcf2127.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/rtc/rtc-pcf2127.c b/drivers/rtc/rtc-pcf2127.c
index 33fa8b17b79c..39a7b5116aa4 100644
--- a/drivers/rtc/rtc-pcf2127.c
+++ b/drivers/rtc/rtc-pcf2127.c
@@ -336,7 +336,8 @@ static int pcf2127_watchdog_init(struct device *dev, struct pcf2127 *pcf2127)
 	u32 wdd_timeout;
 	int ret;
+	    !device_property_read_bool(dev, "reset-source"))
 		return 0;
 	pcf2127->wdd.parent = dev;

Powered by blists - more mailing lists