From: Moritz Fischer <mdf@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: moritz.fischer@ettus.com, linux-watchdog@vger.kernel.org,
linux@roeck-us.net, wim@iguana.be, a.zummo@towertech.it,
alexandre.belloni@free-electrons.com, rtc-linux@googlegroups.com,
alex.williams@ni.com, Moritz Fischer <mdf@kernel.org>
Subject: [PATCH 0/2] DS1374 Watchdog fixes
Date: Mon, 24 Apr 2017 15:05:10 -0700 [thread overview]
Message-ID: <1493071512-5718-1-git-send-email-mdf@kernel.org> (raw)
Hi all,
this series fixes two issues that I ran into when trying to use the
watchdog part of the DS1374 on of our products.
This series is basically a precursor to some further cleanup work,
that turns the DS1374 into a MFD device with an RTC and WDT in
separate drivers [1] each integrated in either the watchdog and
the rtc frameworks.
I'm very unhappy with the CONFIG_DRV_RTC_DS1374_WDT way of enabling
the watchdog behavior and currently I'm investigating how to make
that work via DT.
Watchdog maintainers, do you have an idea on how to do that in a
non breaking fashion?
Thanks,
Moritz
[1] https://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux.git/log/?h=wip/mfd-ds1374-rfc
Moritz Fischer (2):
rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt
ticks
rtc: ds1374: wdt: Fix stop/start ioctl always returning -EINVAL
drivers/rtc/rtc-ds1374.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-24 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 22:05 Moritz Fischer [this message]
2017-04-24 22:05 ` [PATCH 1/2] rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt ticks Moritz Fischer
2017-05-04 12:47 ` Alexandre Belloni
2017-04-24 22:05 ` [PATCH 2/2] rtc: ds1374: wdt: Fix stop/start ioctl always returning -EINVAL Moritz Fischer
2017-05-04 12:47 ` Alexandre Belloni
2017-04-25 5:03 ` [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck
2017-04-25 14:55 ` Moritz Fischer
2017-04-25 16:17 ` Guenter Roeck
2017-04-25 16:32 ` Alexandre Belloni
2017-04-25 16:58 ` Guenter Roeck
2017-04-25 19:58 ` Moritz Fischer
2017-04-25 20:22 ` Guenter Roeck
2017-04-25 20:34 ` Moritz Fischer
2017-04-25 21:05 ` Guenter Roeck
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=1493071512-5718-1-git-send-email-mdf@kernel.org \
--to=mdf@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alex.williams@ni.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=moritz.fischer@ettus.com \
--cc=rtc-linux@googlegroups.com \
--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;
as well as URLs for NNTP newsgroup(s).