[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200924105256.18162-1-u.kleine-koenig@pengutronix.de>
Date: Thu, 24 Sep 2020 12:52:54 +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 0/2] rtc: pcf2127: only use watchdog when explicitly available
Hello,
now that there are two people stumbling over the pcf2127 driver
providing a non-functional watchdog device, here comes an RFC patch to
address this.
Note this is only compile tested and dt-documentation is still missing.
Still send this series because the cleanup is nice independent of this
discussion and to have something to argue about.
Does someone can offer a better name than "has-watchdog", is there a
scheme that could be used already that I'm not aware of?
Best regards
Uwe
Uwe Kleine-König (2):
rtc: pcf2127: move watchdog initialisation to a separate function
[RFC] rtc: pcf2127: only use watchdog when explicitly available
drivers/rtc/rtc-pcf2127.c | 57 ++++++++++++++++++++++-----------------
1 file changed, 32 insertions(+), 25 deletions(-)
--
2.28.0
Powered by blists - more mailing lists