From: "Johnson CH Chen (陳昭勳)" <JohnsonCH.Chen@moxa.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
Lee Jones <lee.jones@linaro.org>
Subject: [PATCH 0/3] Use MFD for Dallas/Maxim DS1374 driver series
Date: Mon, 22 Jun 2020 10:03:25 +0000 [thread overview]
Message-ID: <HK2PR01MB3281DAE412911621A7F8963BFA970@HK2PR01MB3281.apcprd01.prod.exchangelabs.com> (raw)
Hello all,
This patch set uses MFD structure for DS1374 so that RTC and Watchdog
functions can be separately. Therefore, we can add more Watchdog
subfunctions here.
A DS1374 MFD core driver supports the I2C communication to RTC and
Watchdog devices.
1. Add DS1374 MFD core driver with I2C bus.
2. Let DS1374 RTC driver has RTC and Alarm functions only.
3. Add DS1374 Watchdog driver.
Thanks,
Johnson
Johnson Chen (3):
mfd: ds1374: Introduce Dallas/Maxim DS1374 MFD core driver
rtc: rtc-ds1374: Move out Watchdog function and I2C client
watchdog: ds1374_wdt: Introduce Dallas/Maxim DS1374 Watchdog driver
drivers/mfd/Kconfig | 11 +
drivers/mfd/Makefile | 2 +
drivers/mfd/ds1374.c | 101 ++++++++
drivers/rtc/Kconfig | 9 +-
drivers/rtc/rtc-ds1374.c | 458 ++++++----------------------------
drivers/watchdog/Kconfig | 11 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/ds1374_wdt.c | 330 ++++++++++++++++++++++++
8 files changed, 532 insertions(+), 391 deletions(-)
create mode 100644 drivers/mfd/ds1374.c
create mode 100644 drivers/watchdog/ds1374_wdt.c
--
2.20.1
next reply other threads:[~2020-06-22 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 10:03 Johnson CH Chen (陳昭勳) [this message]
2020-06-22 11:25 ` [PATCH 0/3] Use MFD for Dallas/Maxim DS1374 driver series Alexandre Belloni
2020-06-23 3:19 ` Johnson CH Chen (陳昭勳)
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=HK2PR01MB3281DAE412911621A7F8963BFA970@HK2PR01MB3281.apcprd01.prod.exchangelabs.com \
--to=johnsonch.chen@moxa.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/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).