[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200924105256.18162-3-u.kleine-koenig@pengutronix.de>
Date: Thu, 24 Sep 2020 12:52:56 +0200
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>,
Qiang Zhao <qiang.zhao@....com>,
Bruno Thomsen <bruno.thomsen@...il.com>
Cc: linux-rtc@...r.kernel.org, a.zummo@...ertech.it,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, robh+dt@...nel.org,
kernel@...gutronix.de, Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: [PATCH 2/2] [RFC] rtc: pcf2127: only use watchdog when explicitly available
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 "has-watchdog"
property.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
---
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 5b1f1949b5e5..8bd89d641578 100644
--- a/drivers/rtc/rtc-pcf2127.c
+++ b/drivers/rtc/rtc-pcf2127.c
@@ -340,7 +340,8 @@ static int pcf2127_watchdog_init(struct device *dev, struct pcf2127 *pcf2127)
u32 wdd_timeout;
int ret;
- if (!IS_ENABLED(CONFIG_WATCHDOG))
+ if (!IS_ENABLED(CONFIG_WATCHDOG) ||
+ !device_property_read_bool(dev, "has-watchdog"))
return 0;
pcf2127->wdd.parent = dev;
--
2.28.0
Powered by blists - more mailing lists